Our task forms contain some items that contain an a!startProcessLink to trigger some actions. Between task assignment and task acceptance these are available to users.
We don't think that this should be the case, as all other components are disabled. We'd like to be able to disable those components as well.
Is there a SAIL based mechanism to identify an unaccepted task? Or, is there another way to achieve this?
Discussion posts and replies are publicly visible
Perhaps you can try referencing tp!owner.
To expand on what David said already - the effective method I've seen for this in the past is to check the value of tp!owner from within the form, as this task instance property is empty prior to acceptance. When empty, you could disable the link or any other interface component that doesn't automatically disable while in this state.
We'll give this a try, cheers!
Cheers, we'll give this a try, thanks for your answer Mike!
Thank you for the expanding on that. Can you elaborate on how I can access tp!owner inside a SAIL form? and also get the tp!owner updated value when a user accepts?
You would pass in tp!owner as a rule input into your interface. As far as I've seen when testing, the value is updated automatically upon user acceptance of an interface.
Thank you. That works as intended for disabling the UI components but doesn't seem to refresh or update the rule input for owner as soon as I click accept, It will update the value if I manually refresh the page.
Can you share more about what you've tried, as far as configuration?
I just made a simple process model and interface, with one Rule Input into which I pass tp!owner from the process model. The task is initially group-assigned to a group I belong to.
As soon as I press "Accept" (i.e. no manual refreshing necessary), the "accepted owner" value populates on my form:
Using on-form logic it should be possible to do any necessary toggles for displayed items/links/controls/etc based on the task's current acceptance status. If this isn't working for you, can you please provide a screenshot of your task's "Forms" configuration tab, and/or relevant portions of your interface code?
Edit: I've updated my example form to actually contain a link and I've recorded a video of the task acceptance process to show how seamless it is, view here.
Thank you it worked after I passed tp!owner directly to the Rule Input instead of passing the tp!owner through the activity class which I did earlier. Thanks !!
Cool, glad it worked for you and thanks for confirming