Revision Management landing page

Use the application overlays facilities to define and manage application overlays, and click Refresh to make sure you are looking at the latest list of application overlays.

The overview shows information about existing application overlays.

• Name: name of the application overlay.
• Created: time elapsed since the application overlay was created.
• Created by: user that created the application overlay.
• Updated: time elapsed since the application overlay was last updated.
• Updated by: user that last changed the application overlay.
• Action: update the rules included in the application overlay
• Use the icon at the end of each row to delete the application overlay. Deleting an application overlay results in removing any associations to the access groups, deleting the access group, deleting the application overlay, the data records and the revision ruleset.

Use the New button to open the Create New Application Overlay wizard. Before running the wizard, make sure there is an available unlocked ruleset. This wizard allows you to create a new application overlay in fours steps:

• Application Overlay: the application overlay is built on the current application, and corresponding version.
  • The Application record section displays the application overlay built on details, and the associated ruleset.
  • Enter the description.
  • Define the name of the revision ruleset.
  • Click Next.
• Access group & roles: users with the access group defined in this step will be able to work with the instances defined in the application overlay through the Decision Manager portal.
  • By default, the wizard lists three default access groups for revision management overlays (decision architect, revision manager and strategy designer). You can remove the default roles and define new access groups by providing a name and selecting one or more roles. Direct deployment overlays list a special role (direct deploy).
  • If the default roles do not meet the requirements for user activity in the Decision Manager portal, configure your own custom roles by using the granular privileges that, combined, define the group of actions for a given role. The following steps also apply if you need to add a new access group to an existing application overlay.
    • Define access of role to object instances using the Decision Manager privileges.
      The available privileges

      Privilege	Description
      pyMonitorADMModels	Monitor adaptive models, monitor predictors and access ADM reports.
      pyUpdateADMReportingData	Update adaptive reporting data.
      pyManageADMModels	Manage adaptive models through the actions that allow for controlling the adaptive data store (clear, delete and train models).
      pyMonitorInteractionHistory	Access reports in the Interaction History category.
      pyMonitorReports	Access the report browser.
      pyTestFlows	Run applications.
      pyMonitorVBDActuals	Use the VBD planner to monitor actuals.
      pyMonitorVBDSimulation	Use the VBD planner to monitor simulation data sources.
      pyManageVBD	Manage KPIs, data sources and views.
      pyRunSimulations	Run simulations.
      pyManageRevisions	View business rules, revisions and work list. Access the revisions facilities.
      pyWorkOnChangeSets	View business rules, work on change requests, open rules, change rules and submit changes.
      pyViewCalendar	Access the Decision Manager portal's Plan facilities.

    •  Associate each access role with the applicable access of role to object depending on the type of user exposure to Decision Manager portal functionality.
    •  Associate each access group with the applicable access role.
  • Click Next.
• Rules: the rules included in this step are placed under revision management. You can select from the built on application's decision data records, decision tables, decision trees, map values, predictive models, scorecards and strategies. The wizard filters out the instances included in another revision ruleset.
  • Select the instances.
  • If applicable, use the Rule type and Applies to column filters to display a selection of the rules available to include in the revision ruleset.
  • Click Include for revision management.
  • Click Next to review the contents of the application overlay.
• Review: review the application overlay settings and supporting assets.
  • The initial section, Review application overlay, displays the settings as defined in the previous steps (application details, revision ruleset, access groups and rules available for revision management).
  • The next section, Review records, displays the list of instances that will be generated when you click Create. This consists of application, rulesets (revision and branch ruleset), pxDecisioningClass fied value, <overlay_name>Revision data instance listing the rules placed under revision management, and access groups.
  • Click Back if you need to make changes in the previous steps.
  • Click Create to create the application overlay.
    • The wizard generates the instances supporting the application overlay, including a development ruleset branch following the <ruleset_name>RM pattern.
    • Additionally, this process results in altering the application record so that it includes the (locked) revision ruleset in its application rulesets list.
    • The process of defining the access groups does not include associating operator records with the access groups. This is a follow up step you need to do so that users can access the Decision Manager portal governed by the exposed functionality as defined in the applicable role.

This tab lists the revisions available in the system. System architects import revisions based on changes packaged by revision managers in the Decision Manager portal.

The overview shows information about existing revisions.

• Application Version: version of the application.
• Overlay: name of the revision ruleset.
• Revision: version of the revision ruleset.
• Packaged by: name of the user (revision manager) that packaged the revision.
• Updated: time elapsed since the last update to the revision.
• Updated by: name of the user that last updated the revision.
• Status: status of the revision.
  • Testing: changes in this revision are being tested by designated users.
  • Active: changes in this revision are active in production.
  • Inactive: a new version of this revision is active.
  • Rolled-back: a revision in production that was rolled-back.
• Action
  • Discard: discard the revision activated for testing.
  • Activate: roll-out to production the revision activated for testing.
  • Roll-back: roll-back a revision that is in production.

Click Import revision to launch the Import Revision Package wizard. The wizard takes you through the process of importing a new revision in four steps:

• Load package
  • If you need to import a new revision, browse to the location where the JAR file is available and import it.
  • If the revision you require is already available in the system, click Next.
• Select package
  • This step lists the revisions available in the server, including the revision you just uploaded. Make sure the revision is selected in the Select package drop-down.
  • Information about the this revision is displayed in theFile information panel.
  • Click Next.
• Review contents
  • Use the information displayed in this step to review the contents of the selected revision.

  • By default, a revision package containing decision data records overrides the values of these parameters in the direct deployment revision package in resolved-activated state (management of direct deployment revisions is done by revision managers in the Decision Manager portal). This behavior can be disabled by selecting the Preserve changes made through direct deployment setting. If you select this option, you discard changes in decision data records included in this package that are also present in the direct deployment.

  • Click Next.
• Test
  • This step displays the users that can test and validate the changes.
  • Select one or more users.
  • Click Test to activate the revision for testing.

The result of running the wizard is a new revision. The status is flagged for testing, and you can check which users are assigned to test the revision.

• Use the Discard action in the Revision Management landing page if the revision was not accepted by the test users.
• Use the Activate action so that these changes included in the revision become the current version.

Note: There is currently no mechanism that oversees the compatibility and synchronization of revisions between environments. Care must be taken to keep the revisions compatible and synchronized.