Admin settings

Use NEX rules for workflow settings

Administrators now have more flexibility for configuring auto-approvals and review rejections in the workflow settings. Network Expression (NEX) Rules can be used to identify specific conditions.

Examples

  • Review rejections on addresses based on the HCP or HCO value.

  • Auto-approve specific sub-objects on HCPs, but not HCOs.

  • Auto-approve add requests submitted by specific users.

  • Auto-approve add requests for HCPs based on the HCP type.

This enhancement is enabled by default. Administrators can define NEX rules for the supported settings.

Supported workflow settings

  • Auto-Approve Add Requests for New Customer Owned Records

  • Auto-Approve Change Requests for New Customer Owned Records

  • Review Master Data Providers (OpenData or Third-Party Master) Rejection of Add Requests

NEX Rule enhancements for workflow settings

To support the ability to define specific conditions for these settings, the following updates are made to Network expressions.

Workflow metadata

The following three fields can be used to in Network expressions:

  • creator

  • system

  • source

Example: Auto-approve Add Requests for HCPs 

if(DCR.creator == 'bob.smith@verteo.veevanetwork.com', TRUE, FALSE)

Use entity level fields in sub-object rules

Create a condition for a sub-object based on a field value for the related entity.

Example - Review rejections for addresses if the HCP is an MD 

ENTITY.medical_degree_1__v in ['MD']

Define NEX rules

  1. In the Admin console, click Settings > Workflow Settings.

  2. Hover over the setting that you want to change to display the Edit button.

  3. Click Edit to display the available options for the setting. Select the option to use NEX.

  4. Enter the Network Expression in the field.

    Tip: Comments can be added to explain the expression or add details for other users.

  5. The NEX rule validates as you type the expression.

  6. Save your changes.

The workflow setting is now to use the NEX rule for that object.

Exporting configurations

Single sign-on (SSO) configurations are no longer supported in configuration packages because they contain environment-specific details that cannot be transferred between instances. SSO settings must be configured within each instance.

This change is enabled by default in your Network MDM instance.

New configuration packages

SSO settings cannot be added to export packages.

Existing configuration packages

If your package included SSO settings, the configuration package will fail when you try to import it to a target instance.

To continue using the package, clone it and remove the SSO settings.