How to make variables mandatory on an SCTASK only AFTER the assigned-to is not empty?

[Roberta B]

Hello,

I have 5 mandatory variables that only the tech should fill in once the auto-generated SCTASK is assigned to the group.

However, the SCTASK cannot be assigned-to a tech until all mandatory fields are completed.   Any ideas how to make those variables mandatory AFTER the assigned-to is not empty? 

Thank you!

[Roberta B · Accepted solution]

@AshishKM  and @-O-  -

I appreciate your response.

I ended up having to create the following new Client Script just for this one catalog item to meet our needs, as a Catalog UI Policy script did not work:

[-O-]

Note that this will fail if form some reason someone removes from the current view the requested_item.cat_item field from the form.

This would be a bit more robust and more generally configurable if you made the Client Script so that it uses data added to g_scratchpad.

Using display business rules you could add both the list of variables to make mandatory and the id of the catalog item to g_scratchpad.

That way it would not matter which fields are or are not on the form, the solution would still work.

[AshishKM]

Hi @Roberta B 

Thanks for sharing details, If you read my previous reply , I suggested for "Catalog Client Script" so you don't need to check the "requeste_item.cat_item" otherwise this client script will execute for all tasks as its running on table level than "catalog item" level.

Thanks for your "appreciation" but you can do more on that to "accepting solution" and marking "helpful".  

[Roberta B]

Thanks for the additional input, @AshishKM.  However, currently we only want this Client Script to run against a specific catalog item and thus used the SysID of that catalog item in the script.   In the future, we may update if/as needed.