Martyn Houghton Posted November 1, 2019 Share Posted November 1, 2019 Can I raise an enhancement request to have the ability to add conditions to the Human Task outcomes themselves, so that there is an option to only provide the Analyst with the option to choose an outcome if a set of conditions is met. This way we can use a more generic Human Task in the workflow, but apply come validation to the outcome when the task is being attempted to be completed. i.e. the option to update a JIRA ticket with a comment is greyed out if the custom field containing the JIRA reference is blank. The aim would be that the conditions are check when then the task is opened to be completed, not when the task is created. Cheers Martyn Link to comment Share on other sites More sharing options...
samwoo Posted November 4, 2019 Share Posted November 4, 2019 +1 this would be great! 1 Link to comment Share on other sites More sharing options...
Guest Paul Alexander Posted November 5, 2019 Share Posted November 5, 2019 +1 for this please..... Link to comment Share on other sites More sharing options...
Martyn Houghton Posted January 26, 2022 Author Share Posted January 26, 2022 @James Ainsworth @Steven Boardman Any update on this? We have got a number of BPM where we want to control the visibility of Human Task outcomes based on the current position of the request. Cheers Martyn Link to comment Share on other sites More sharing options...
Martyn Houghton Posted March 10, 2022 Author Share Posted March 10, 2022 @James Ainsworth @Steven Boardman Is this being considered? As having conditions on the Human Activity tasks outcome would allow us to use less complex workflows which are more context aware. Cheers Martyn 1 Link to comment Share on other sites More sharing options...
James Ainsworth Posted March 10, 2022 Share Posted March 10, 2022 Hi @Martyn Houghton I'm not aware of this being considered at the moment. I'll feed this back to the development team. Link to comment Share on other sites More sharing options...
James Ainsworth Posted March 11, 2022 Share Posted March 11, 2022 Hi @martyn, While Custom Buttons on Request are directly related to a request as the feature is built into the request itself, The task and the request are two separate entities. Tasks can also be associated to other entities, such as an organisation or a project. Tasks just do not hold the information about the entities that they are attached to in order to add a feature for conditions that would need to interact with any number of entities that the task may be associated to. With this in mind, we wont be looking to implement this feature. Link to comment Share on other sites More sharing options...
Martyn Houghton Posted March 15, 2022 Author Share Posted March 15, 2022 @James Ainsworth I am referring to the 'Human Task' object created and defined in the BPM which has a controlled context, rather than a generic activity which can indeed be created against multiple object types. For example in a BPM task, if a custom field is already populated with a value, i.e. a development reference, we would not want the 'Log with Development' outcome to be available, as it is already been done. Cheers Martyn Link to comment Share on other sites More sharing options...
Steve Giller Posted March 15, 2022 Share Posted March 15, 2022 43 minutes ago, Martyn Houghton said: I am referring to the 'Human Task' object created and defined in the BPM On 3/11/2022 at 3:49 PM, James Ainsworth said: Tasks can also be associated to other entities, such as an organisation or a project. The Task is created within the BPM, which is what associates it to a Request. It is not part of the Request. If a Project BPM created it, it would be associated to a Project - etc. Like a caravan being pulled by a car, the two are linked but the Caravan is not part of the car, and could just as easily be pulled by a Van, a Lorry, or even a horse and cart. Link to comment Share on other sites More sharing options...
Martyn Houghton Posted March 16, 2022 Author Share Posted March 16, 2022 @Steve Giller @James Ainsworth But when task is created by the BPM, the conditional Outcome would be be specified on creation. i.e. the change to the definition of the Task and it's Outcome is derived and modified before the Task is actually created. i.e. the caravan does not know that it could have had 4 optional elements instead of 3. Cheers Martyn Link to comment Share on other sites More sharing options...
Steve Giller Posted March 16, 2022 Share Posted March 16, 2022 No, that would be like saying "If I hitch the caravan to a motor vehicle it has four wheels, but if I hitch it to a horse it has two." Link to comment Share on other sites More sharing options...
Martyn Houghton Posted March 18, 2022 Author Share Posted March 18, 2022 @Steve Giller Appreciate what you saying, but the activity object/entity already has the multiple configuration options within it for when it is spawned from the different sources. Activities created from a BPM have outcomes, those created as manually activities do not. A BPM activity can have any number of outcomes depending on the setup in the BPM. As far as I understand the activity is created by the BPM each time it is reached in the workflow, not when the workflow is originally spawned? Therefore creating the activity with less outcomes that defined is a matter of adjusting the activity creation process to filter out the non-required outcomes based on the conditions set. Not saying it easy, but it should be possible? Cheers Martyn Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now