Numerous variables missing from catalog task (SCTASK) form after Catalog Item submission.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-11-2018 12:48 PM
Hello, I've noticed that lately numerous variables from my catalog item are missing from catalog tasks created from the workflow activities.
Things I've checked:
- This doesn't appear to affect any other catalog items.
- There are a couple of others with a very large list of variables appearing on the task level which aren't affected.
- The list of variables that loads seems to be intermittent.
- Sometimes a good chunk show on the form, other times, very little show. This happens on the same type of form submission using the exact same data.
- I've added (and removed / readded in some cases) the variables to the catalog task activities in the slush bucket.
- The variable editor is present on the form layout.
- The variables are all global. (I need them to appear on both levels.)
- The UI policies showing / hiding some variables are set to act on both the Catalog Task and Requested Item levels.
- The only Catalog client script acting on variables in this form (besides some enforcing due dates), acts on all variables to make them read-only unless users have a certain role.
- I've tried completely deleting this, but it doesn't seem to affect the issue at all.
They were working fine until a while ago (maybe a couple of weeks - just alerted to this recently by some users, it is a rather intelligent form that is still in testing phases).
Does anyone have any thoughts on what I should check out? I'm at a loss to be honest.
- Labels:
-
Request Management

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-07-2019 10:05 AM
You weren't kidding about this being old. I think my issue ended up being due to the amount of variables the system would allow on the catalog task at the time. If I remember right, I updated it from its previous limit to something like 400 and it was good to go.
As for your issue, glad you got it resolved. I messed with that stuff occasionally when I was trying to figure out a good way to hide variables on the portal, but never really found a good solution there. Best thing I could do was change read rights on the variable so normal end users couldn't see it.