AnsweredAssumed Answered

Customize Change Descriptions

Question asked by William May on Nov 6, 2018
Latest reply on Nov 9, 2018 by William May

Like • Show 0 Likes0
Comment • 7

Is it possible to customize the text of this email variable to include other attributes that you want to communicate to the recipient?

${jobUserData_CHANGE_DESCRIPTION}

I believe the current output is something like this:

Remove account apple from group SALAD Access Group

I'd like to include the account user name or some other attribute to help system admins enter it into their provisioning system (they can only lookup by user name in this example).

Also, I cannot just add something like ${access_request_cri_meu_firstName}, because these requests are grouped to send multiple items in the same email, so above variable would be a comma separated list of user first names, for example.

Thanks,

Bill

7.0.2 P07

No one else has this question

Outcomes

7 Replies

Boris Lekumovich Nov 6, 2018 7:22 PM
Mark Correct
Correct Answer
The variable you mentioned (${jobUserData_CHANGE_DESCRIPTION}) looks like a custom variable that you created in the workflow rather than the out of the box variable. So in theory, you can customize the text to your needs.
See similar post - Workflow Email HTML Variable
Like • Show 0 Likes0
Actions
- William May @ Boris Lekumovich on Nov 8, 2018 5:58 PM
  Mark Correct
  Correct Answer
  Yea, I got further clarification that it's the AVUSER. PV_CHANGE_REQUEST_DETAIL.CHANGE_DATA_DESCRIPTION that he custom variable is targeting.
  
  That's ideally what I'd like to control/customize.
  Like • Show 0 Likes0
  Actions
  - Boris Lekumovich @ William May on Nov 8, 2018 6:19 PM
    Mark Correct
    Correct Answer
    Rather than customizing/controlling that out of the box value, I would create a SQL query to gather the relevant information from the different views
    And in the email node just use that new variable with the custom content
    Like • Show 1 Like1
    Actions
  - William May @ William May on Nov 8, 2018 6:20 PM
    Mark Correct
    Correct Answer
    I read through the other link too - I think I have my plan... need to do more testing, but seems I could just replace with this instead of the raw DB Value:
    
    SELECT crd.Change_Data_Description
    || ' (User: ' || U.First_Name || ' ' || U.Last_Name || ', ' || U.Email_Address || ')'
    FROM AVUSER.Pv_Change_Request_Detail crd,
    AVUSER.Pv_Users U
    WHERE Crd.Affected_User_Id = U.ID
    AND crd.Change_Request_Id =57227;
    Like • Show 0 Likes0
    Actions
Mostafa Helmy Nov 7, 2018 8:46 AM
Mark Correct
Correct Answer
I believe the actual variable you are referring to is ${access_request_details} which contains a bullet point list of change items in a similar format to what you mentioned above.

However there isn't a way to change its format. Sounds like a good idea to post on RSA Ideas.
Like • Show 0 Likes0
Actions
Andy Cheek Nov 9, 2018 10:51 AM
Mark Correct
Correct Answer
The other (another) thing to bear in mind is that the CHANGE_DATA_DESCRIPTION field is constructed using the alternate display name for entitlements. If, like us, you want the RAW name as that is what the application actually recognises, then that field is next to useless. That then means constructing your own version of the changes, which potentially means taking all the different types into account and resolving the VALUE & OPERAND ids accordingly.

Thanks are better now, however, since the AFFECTED_USER_ID field was added to PV_CHANGE_REQUEST_DESCRIPTION and the PV_UNIFIED_ENTITLEMENT view.

Be warned though - the new way of holding arrays in WF variables has changed so you may find some spurious commas being displayed in your email !
1 person found this helpful
Like • Show 0 Likes0
Actions
- William May @ Andy Cheek on Nov 9, 2018 11:17 AM
  Mark Correct
  Correct Answer
  Thanks Andy for pointing out some of the pitfalls to avoid! I was unaware that the alternate display name was being used in that variable.
  Like • Show 0 Likes0
  Actions

Customize Change Descriptions

Outcomes

Related Content

Recommended Content