New

Dynamic selection of workflows based on selection in PCF/API

Currently you can only set 1 default workflow in a Customer/Contact Project Template to be auto applied when new projects are created through the PCF / API.

It would be useful to allow for setting multiple default workflows, depending on what Service (or other trigger) is selected by the customer. For example, if the customer selected 'Translation Only', it would use a pre-made 'Translation Only' workflow template, but if the customer selected 'Translation and Proofreading', it would select a different workflow template to auto apply.

Parents
  • Hi Tom, this is what the "Services List" does. Make sure to name your workflows in a public/customer-facing manner, and then the customer is literally choosing 'Translation Only' or 'Translation and Proofreading' or whatever. This works for both the older and the dynamic workflow templates.

Comment
  • Hi Tom, this is what the "Services List" does. Make sure to name your workflows in a public/customer-facing manner, and then the customer is literally choosing 'Translation Only' or 'Translation and Proofreading' or whatever. This works for both the older and the dynamic workflow templates.

Children
  • Hi Shirley,

    Thanks for the reply.

    Where do you set the services options? I was looking in the Project Template for a customer and can't see how I can add more than 1 dynamic workflow.

    Is specifying a service available through the API? SOAP / REST? So for example, in the API call set the 'service' which would decide which workflow to select.

    Tom

  • Hi Tom,

    Discussed offline, but I'll post a brief summary here for anyone else interested. 

    Both the legacy and the dynamic workflows have the option, per workflow, to "Show in PCF". Selecting this option adds the workflow name to the "Services List" which is a part of the default PCF (can be added or removed in the usual manner). When the user selects a service from this list, from the Customer Portal, they are effectively selecting their workflow.

    This is also accessible via the serviceName in createProject in the REST API.

    Shirley