Aras DevOps

Aras DevOps now supports deploying Aras Innovator instances with Edge Eventing and AI Search enabled via standard Aras DevOps pipelines.

New Behavior:

• If SDE is entitled for AI Search and Edge Eventing usage, then all deployments automatically includes the newly enabled components.
• Existing production environments can be updated via the standard Aras DevOps pipelines.
• New versions of AI Search and Edge Eventing are automatically delivered.

Benefit:

• Customers gain access to AI Search and Edge Eventing capabilities without manual repository changes.

CI/CD pipelines now copy a pre-loaded baseline database from Azure SQL instead of restoring it from a .bacpacfile on every run.

New Behavior:

• The pipeline checks whether a baseline database already exists in Azure SQL Elastic Pool.
• If baseline found, the database is copied directly completing significantly faster than a .bacpacrestore.
• If baseline is not found, the .bacpacis restored once and preserved for future runs.
• Applies to SaaS environments.

Benefits:

• Reduces CI/CD build time. Previously, restoring a baseline from .bacpac grew longer as customer metadata accumulated. Baseline database preparation during CI/CD is now faster.

Customer repositories now store only customer-specific AML changes in metadata instead of storing both released with Innovator AML packages and customizations.

New Behavior:

• New repositories are created with no AML files in the AML packages folder by default — only a README and an empty import.mfare presented.
• Updating to Aras DevOps 1.15 removes all Innovator AML packages that are unchanged compared to the released AML artifact, preserving only customer customizations.
• Released Innovator AML packages is no longer stored in customer repositories. They are already available in the database by default. During upgrades, if a new package is missing from the database, it may be placed back into the repository.

Benefit:

• Reduces repository size, eliminates unnecessary AML-related merge conflicts, and makes Git diffs clearly reflect only what the customer has customized.

Each Innovator deployed via Aras DevOps now automatically creates a corresponding CIAM application, eliminating manual CIAM setup, if CIAM integration is enabled for SDE.

New Behavior:

• A dedicated CIAM Application is created automatically per Innovator at deploy time, with usable default configuration.
• Removing an Innovator via Aras DevOps automatically removes the corresponding CIAM Application.
• Re-deploying the same environment does not create duplicate CIAM Applications.
• CIAM administrators can further modify the generated application after creation.
• Applies to UAT, SIT, STG, and Production environments.

Benefit:

• Simplifies SSO configuration with automatic CIAM Application creation, if CIAM integration is enabled for the SDE.

New-ArasDevOpsRepository now enables the Automatic Resolve Item Dependency feature for all newly created SDEs.

New Behavior:

• The following property is set automatically in default.settings.includefor new repositories:
  <property name="Import.AutoResolveItemDependency” overwrite="false” value="true"/>
• Existing customers updating their repository retain their current setting.

Benefit:

• New customers benefit from this feature immediately, without additional manual configuration.

The default configuration provided by the Aras.Devops module can be overridden if needed.

New Behavior:

• SetupEnvironment.config.jsonis read from the customer repository, if present.
• If the file is not present in the repository, Aras DevOps falls back to the version shipped with the Aras.Devops module.

Benefit:

• Gives control over environment setup configuration without requiring changes to the Aras DevOps module itself.
  

All Aras DevOps scripts in the Local Development Environment (LDE) and all Aras DevOps PowerShell module commands now support the -helpoption.

Now it is possible to discover available parameters and options inline, without consulting documentation, reducing setup friction in the LDE.

The BuildAndDeploy.ps1 script now includes logic to verify the presence of necessary baseline in the configured local path. If this artifact is missing, the script automatically downloads it from the project’s universal feed.