what is it mean for display name is not dynamic?

  Discussion posts and replies are publicly visible

Parents
  • 0
    Certified Lead Developer

    Hi,

    In Process Properties, by default the process display name will be process model name given while creating but you need to have display name dynamic so that each process instance can be uniquely defined. In order you to make it dynamic, try appending any unique identifier for that process. For example, request id, ticket id etc.

  • how to make display name dynamic? do you mean process model name have to be different as display name?

  • 0
    Certified Lead Developer
    in reply to immortalvirgil

    You can make it dynamic by appending a unique identifier used in that process model. Something like a request id. For Example, if your process model named "Edit Request" is used to edit a request, the display name should be something like "Edit Request# "&pv!requestId. Hope this helps!

    Please go through below link from documentation for further details

    docs.appian.com/.../process-model-object.html

  • Let's start with some basics:

    1. a Process Model is a "template" from which Process instances can be created
    2. a Process Model has various attributes, including:
      1. the 'Process Model Name' which is static (you can change it but only as a design-time activity)
      2. the 'Process Display Name' - this is what will be used to display the name of an instance of a process model in the 'Process Activity' tab of  'Monitoring' option in the Appian Designer. 
    3. When you create a Process Model Appian defaults the 'Process Display Name' to the same value as the 'Process Model Name' but it is best practice to make the Display Name dynamic, so that, in Production, the Support Team can disambiguate between instances. Typically I create a rule that concatenates the Process Model name with a relevant unique business value, something like this:

    fn!concat(
        ri!processModelName,
        " for Opportunity ",
        ri!opportunityName,
        " for Account ",
        ri!accountName
      )

    Note: when you call such a rule form the 'Process Display Name' use the pm!name value to set the ri!processModelName to in case someone decides to change the Process Model name in the future.

Reply
  • Let's start with some basics:

    1. a Process Model is a "template" from which Process instances can be created
    2. a Process Model has various attributes, including:
      1. the 'Process Model Name' which is static (you can change it but only as a design-time activity)
      2. the 'Process Display Name' - this is what will be used to display the name of an instance of a process model in the 'Process Activity' tab of  'Monitoring' option in the Appian Designer. 
    3. When you create a Process Model Appian defaults the 'Process Display Name' to the same value as the 'Process Model Name' but it is best practice to make the Display Name dynamic, so that, in Production, the Support Team can disambiguate between instances. Typically I create a rule that concatenates the Process Model name with a relevant unique business value, something like this:

    fn!concat(
        ri!processModelName,
        " for Opportunity ",
        ri!opportunityName,
        " for Account ",
        ri!accountName
      )

    Note: when you call such a rule form the 'Process Display Name' use the pm!name value to set the ri!processModelName to in case someone decides to change the Process Model name in the future.

Children
No Data