Skip to content

Artifact Rule Explanation

Jump to bottom
Brendon Colburn edited this page Jun 13, 2018 · 4 revisions

Figure 1: An example artifact rule list

Figure 2: An example artifact rule

An Artifact Rule is an entity record that defines a scenario in which an artifact should be created along with details about metadata that should be populated on the generated artifact. The list of Artifact Rules is the engine that drives Artifact Management Solution in a given Dynamics 365 CE Organization. Artifact Rules consist of the following attributes:

  • Name - The name of the rule. Best practice is to have this be a combination of Artifact type and the context in which the rule runs.
  • Artifact Type - A customizable option set that contains the artifact types for an organization.
  • IsMandatory - Can be leveraged using portal customization to force a portal user to upload a file to said the generated artifact to proceed.
  • Parent Record - Specifies the parent record to listen for in create and update event scenarios.
  • Related Record - Specifies the related record to listen for in create and update event scenarios.
  • Question Identifier - The schema name of the attribute on the parent record, or the related record if specified, that gets checked on change of the parent/related record
  • Success Indicator - The attribute value of the question identifier that results in an artifact being generated for the parent/related record

Note: If you leave the question identifier and success indicators blank, this rule will generate and artifact every time a parent/related record is created.

  • Specifier Lookup - If necessary, a specifier lookup can be provided that states that the Association of the artifact should be populated using a related record to the parent record using the lookup schema name
  • Specifier - Dictates the Association of the generated artifact. Executes in 3 contexts:

Static - Entering a specifier that is surrounded with "quotes" a string literal is set as the association of the generated artifact.

Parent/Related Record Specific - If the specifier doesn't require a lookup (the attribute lives on the parent/related record) entering the the schema name of the attribute results in it's value being populated as the association of the generated artifact.

Lookup Specific - If a specifier lookup is provided, the schema name specified results in the attribute value on the lookup record populating the generated artifact

  • Portal Comments / Instructions - The detailed instructions to be populated for all artifact generated under this rule
Clone this wiki locally