Loading
Visual Studio Code Based Modeler for Consumer Goods Cloud
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Considerations, Limitations, and References for a Node

            You are here:

            1. Salesforce Help
            2. Docs
            3. Visual Studio Code Based Modeler

            Considerations, Limitations, and References for a Node

            There are certain standard checks to be performed for each node while creating, cloning, or modifying a process contract.

            Ensure that:

            • Each node has all the mandatory Attributes and Subnodes.
            • Each does not have any unknown Attributes and Subnodes.
            • Each node conform to the multiplicity of nodes.
            • For each Attribute, the content is matched with the defined data type.

            This table lists all other validations for Process Contracts:

            SectionsValidations
            Process.Entry.ProcessContext.Declarations.Declaration.name

            Declaration node name is unique in the list of all node names and can’t be:

            • "get" + name of any another node
            • "set" + name of any another node
            • protected FW Method Names
            • Process.Entry.EntryActions.Action.name
            • Process.Body.Actions.Action.name

            Action name is unique in the list of all node names for:

            • Entry.EntryActions
            • Body.Actions
            Process.Body.Actions.Action.Events.name Event name is unique in the list of all names per action.
            • Process.Body.Actions.Action.Events.action
            • Process.Entry.EntryActions.Action.TransitionTo.action
            • Process.Body.Actions.Action.TransitionTo.action
            • Process.Body.Actions.Action.Case.action
            		 Action with the given name exists in the process.
            • Process.Entry.EntryActions.Action.Return.name
            • Process.Body.Actions.Action.Return.name
            • Process.Body.Actions.Action.MasterList.name
            • Process.Body.Actions.Action.DetailObject.name
            		 Declarations.Declaration with the given name exists in the process.
            • Process.Body.Actions.Action.Case.name
            • Process.Body.Actions.Action.Cases.Case.name
            		 Case name is unique in the list of all Case names of the action.
            • Process.Body.Actions.Action.@process
            • Process.Body.Actions.Action.Parameters.Processes.Process.@process
            • Process.Entry.EntryActions.Action.Parameters.Processes.Process.@process
            		 A process can be used as an attribute within an action element. The process has a valid process reference in the module.
            Process.Body.Actions.Action.UIDescription UIDescription node references a valid user interface in the module.

            Sample references from and to Process Contracts:

            FromToPathAnnotation
            Process UserInterface Process.Body.Actions.Action.UIDescription.#Value# UserInterface associated with Process.
            Process BusinessObject / ListObject / ListItem / LookupObject / Domain (including nested SimpleProperties of BO / LO / LU) 
            Process.Entry.ProcessContext.Declarations.Declaration.type
(
Process.Entry.EntryActions.Action.Parameters.Input.value
Process.Entry.EntryActions.Action.Return.name
) only indirectly
            		BusinessObject / ListObject / ListItem / LookupObject / Simple variable
             
            Loading
            Salesforce Help | Article