Hiding Specific RITM Variables in the Approval Emai

Burhan Shah
Tera Contributor

Dear Community,

 

I have built a catalog item with 18 variables. 9 of them are meant for some users, and the other 9 variables are for some different users.

 

We design the workflow to obtain approvals in phases. The first 9 variables should be visible to the first group of approval, and the remaining 9 should appear only to the second phase of approvers.

 

How can I hide them from each other in the approval process?

 

Looking forward to your kind support and expertise.

 

Regards,
Burhan Shah

1 ACCEPTED SOLUTION

Hi @Burhan Shah,

The order guides can handle two different catalog items - you can relate them with the requested for user variable. 

In terms of sequential fulfilment - this can be done: Configure a sequence to fulfill items in order guides

View solution in original post

10 REPLIES 10

Burhan Shah
Tera Contributor

Hi @GlideFather & @Hanna_G 

Actually,, that was the first thing that popped up in my mind, to have two separate RITMs. But how to group/bundle them as one?

We will have reporting/tracking issues in the future.

Regards,
Burhan

@Burhan Shah 
what do you mean bundle them?

There will be "Record Producer" 1 visible for people from Canada only, and "Record Producer" visible for the rest of the World.

They will have the same categories, everything, except of the variable options, that it what will differ.

Eventually if you still want to continue with one record producer only, you can add onLoad catalog licent script with addOption() and removeOption().

Something like:

if('specify_your_condition_here){

g_form.addOption('field_name','choice_name');
g_form.addOption('field_name','choice_name');

g_form.removeOption('field_name','choice_name');
g_form.removeOption('field_name','choice_name');

}

else { 

g_form.addOption('field_name','choice_name');
g_form.addOption('field_name','choice_name');

g_form.removeOption('field_name','choice_name');
g_form.removeOption('field_name','choice_name');

}

 

 

Please refer to this:

KamilT_0-1752047061481.png

KamilT_1-1752047087645.png

As seen in here:
https://www.servicenow.com/docs/bundle/yokohama-api-reference/page/app-store/dev_portal/API_referenc...

———
/* If my response wasn’t a total disaster ↙️ drop a Kudos or Accept as Solution ↘️ Cheers! */


Hi @GlideFather 

What I meant for bundling them together was Order Guide.

What I did yesterday, in the permission tab of the variables, I created a role and restrict it to a specific rule, and the first part worked perfectly fine. Now I have to do the vice versa for the 2nd part.

Regards,

Burhan

Hi @Burhan Shah

When I mentioned Bundle - my approach would have been a catalog item Order Guide. Where you can add both of the Catalog Items under: 
Order guides
Solved: Difference between order guide and catalog item. - ServiceNow Community

You can put both of the catalog items into one RITM, but when submitted they would function as two - so separate approvals etc. Whatever you add in their Flow etc. 


Hello @Hanna_G 

 

Can the order guide accommodate totally different forms for two RPs? Apart from that, can it wait for the first RP to finish and then start the workflow of the 2nd RP?

What I understood from the documentation is that it's rule-based and must have matching variables. In our case, the variables are different.

Regards,
Burhan