Allow all settings of a class property to be overridden in a workflow step - i.e. visibility and readonly

It would be very helpful to allow all properties of a class to be edited in the permissions of a workflow.  For example to have a field that is set to hidden in the class be its default behavior, and then be able to make it visible in the workflow step.  That would prevent me from having to make sure I hide it in every step but the one where I need it.  

I could also see this in terms of a property being read-only.  There may be a single step where it needs to be populated and then not modified again for the rest of the workflow.

0

Comments

4 comments
  • Still interested in this feature. Another way to think about this is for the visibility to be different when displaying the UI vs. whether it displays in the workflow notification.

    0
    Comment actions Permalink
  • Thank you for your contribution Arlette. Did you try the calculated settings which should allow you to configure this granularity for mandatory, visibility and read-only?

    0
    Comment actions Permalink
  • The calculated fields are fantastic and I love them. But this is a little different. I have use cases where I would like something to show up in an email, but not in the UI.  There are times we capture information that is summarized or particularly formatted information that is just for email display purposes, and has no value to be shown in the UI.

    0
    Comment actions Permalink
  • So - I think I misunderstood what is going on with the calculated fields. I had thought they impacted both the UI and the workflow - but I see that is not the case? The calculated field visibility ONLY affects the UI and has no impact on what shows up in the emails, is that correct?

    0
    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post