Workflow Ideas

jumpaolo · ‎11-12-2020

Hi, it would be nice to have the possibility to display in Workflow List (services/workflow/workflows?tab=flows) the "Workflow Triggers". This help us to see if the WF is Scheduled, OnDemand or Callout, without enter in each single detail of the workflow. Thanks

msonsma · ‎05-29-2020

A task edit pane now shows three options for each parameter value: [input], [workflow], [custom]. It should be extended with a fourth option: [Payload] that opens the payload browser ( as available in the swimlane mode ) showing the actual payload available based on the last run. If no payload is available - for instance when you added a new task - it should show the first available payload up-stream Double clicking a node in the payload browser should insert the full path of that node in the field/cursor location. The option to open the payload browser should not be limited to a task's parameter fields only; it should be available on each task's field in which payload fields can be referenced. Benefits: - Clear view of payload nodes/variables available for a task - Clear indication of what kind of data is stored under the nodes - No case typos in node names as you can select them in the payload browser - Quicker developing of workflow as you don't have to switch back and forth between the workflow edit mode and the swimlane mode. - Quicker developing of workflow even in de swimlane mode as you don't have to close the (instance/workflow instance) task configuration box in order to a) move it out of the way as it can overlap the payload pane and/or b) expand a node in the payload pane.

msonsma · ‎05-28-2020

There should be option to store a configured task as a template so it can be easily reused. For instance if define a callout for a particular service and what to use that service multiple times in your work flow or other workflows you now must copy paste the code from one task to another task ( using two browser windows etc ....very awkward, annoying and error prone) By storing a task as a template you reused that taks more easily ( like a lego brick) . By implementing template parameters - where you can map a payload variable to a parameter requried by task script/code the task can re used in the same way as a OOTB task for Zuora CRUD actions...

pask · ‎02-24-2020

Hi, we are developing a tool for importing and exporting workflows using Official Zuora REST API. We used: 1) Get Workflows: to get all workflow Ids 2) Export a workflow: to export all workflows 3) Import a workflow: to import workflows We are using workflow name as key to communicate to an external system. So when we develop a new workflow version and we need to update the existing one there is no api that automatically updates the older version. We need to rename manually the previous version and then import the newer one. Can we request an official api to rename a workflow? Thanks in advance

msonsma · ‎05-28-2020

If you are in swimlane mode and edit and re-run an "Instance Task config" to iron out the error issue's, it would be handy to have an option to sync those changes back to the Workflow Task Config. And when you leave the swimlane mode, a warning like "You have made changes to the instance task config. Are you sure you don't want to apply them to the workflow task config ?"

msonsma · ‎05-28-2020

Would be nice to have an option to protect a workflow from being (partially) copied and distributed without permission of the IP holder. Should be possible to compile a workflow in some encrypted/password protected form and link/license it to specific Zuora tenant(s). ( similar to SFDC managed packages )

sHruschka · ‎12-19-2019

It should be possible to overwrite the JSON file of an exisiting Workflow. Currently we can only import JSON file for initial creation of an workflow but not for update. If we for example want to rollout changes on a workflow we only 2 possibilities: 1.) Remember all the single steps we performed in the UI and do the same again on PROD UI 2.) Import the workflow as new workflow and change all API calls which are referring to the old ID. We have several workflows running on the system which are triggered via API or Notification Events. The API Call requires the workflow ID, which is changing everytime if we use the existing export, import possibilities. Both possibilities are annoying and error prone. Therefore it would be great, if it is also possible to overwrite existing workflow by editing/overwriting the JSON.

Yoshihisa · ‎06-04-2019

There is a request that it is needed to use external smtp server for sending emails through workflow.

JamesQSR · ‎11-11-2019

We use Workflow to provision access to external systems. Sometimes this access is not provisioned because the workflow had issues, or required fields were not properly entered etc. When searching for a specifc run, to find out what went wrong, is only one option: skim through looking at the date/time to see when the workflow should have been called, looking for any with errors There is a search workflow option, but this only really works for looking up Workflow names, or Run Numers - any data within a run e.g. Acccount Number is not searchable We want to be able to record the Workflow Run Number that managed that task and then save it against certain objects (e.g. Subscription, Invoice) - either as a custom field, or to have some logging that would allow this to be linked directly. Example: On Payment received, Workflow A runs to provision access When Workflow A starts, the RunNumber will be recorded/linked on the Invoice/Payment object If there are any issues preventing the workflow running, I can find the Invoice/Payment object - click on the Run Number, and go straight to the run history to see if there were any issues

pask · ‎10-08-2019

Hi, in some cases there is the need to have a shared memory between on start and on finish tasks inside zuora workflow. For example if we do some operation on a set of object interating over them in the start task and we want using on finish to do a specific operations on this data that could be an update or whatever we would like to avoid to query the data again. Thanks in advance.

Emmanuel · ‎06-06-2019

Currently when using a XML transform task, even when specifying and output of txt (not text btw) or csv, the transform actually always generate a xml header line: <?xml version="1.0"?> This forbids the creation of csv of text files with specific formats, and files needs to be re-processed outside of the workflow to remove that line... We should ideally support true output as "text"...

pask

Hi, It would be very useful to have a REST API to Update a workflow. In particular we need to update workflow name and scheduled checkbox. But in general it would be nice to update the whole workflow structure. Thanks in advance Pasquale

pask

Hi, we noticed that using Liquid tester we have to use Chrome inspect element in order to copy the output. Could we receive an enhancemt that consists in creating a dedicated area in which all output that we have in liquid Tester could be copied in a user friendly way? Also a tab in which we could see all variables that we define in the tester could help. A tab containing all functions/filters that we can use in liquid with a short description related to input/output. Thanks in advance Pasquale

pask

Hi, we are receiving a lot of workflow notifications related to async task exhausted. We used DQ everywhere in the system because it is the only functionality in Zuora that enables us to do join and complex SQL queries. It also enables us to reduce task number. For online flows starting from notifications for example we should substitute DQ with a chaining of direct sync query/REST APIs and rearranging data using JSONata simulating all joins (to be honest sometimes we do not have a direct rest api to retrieve the same data) but in this way we have to mantain and fix two version of the same workflow a massive one using DQ and a non massive using sync API. What I am trying to suggest is: Creating a wrapper that receives in input a DQ and transforms in some way it in a sync call without changing our SQL query. In this case we can write our query once and we mantain/fix our logic once and we will have the possibility to have a workflow task/REST API that automatically switches to sync mode based on a dynamic selectable checkbox. Thanks in advance Pasquale

pask

Hi, could I suggest to create a checkbox in each workflow task that enables us to manipulate dynamically task JSON request body (for example In workflow json each task have its static structure, we would like a way to change this structure at runtime) ? Sometimes we need to dynamically select files and we need a way to pass them dynamically to MergeCSV task overriding the static pre-configured ones. Thanks in advance Pasquale

sayam

Hi All, I recently had a requirement where I needed to browse through tonnes of WFs and figure out a specific one. For the use case s ay a WF runs for an account on a subscription(may create/update/delete). This WF runs multiple times every day. Now to find a particular instance of the WF run where it processed a particular subscription is too hard to find (as there are so many). The idea is that in the tasks tab, you enter the ID processed via tha WF and you would know from history whether or not WF was run for that particular ID

dduff · ‎12-02-2020

Workflow offers several advantages over the standard notification emails, but we would like the ability to see the emails sent from Workflow on the account page, similarly to how they can be seen if Notifications fire the email. Without this functionality we must set up a system outside of Zuora for tracking sent emails and there are gaps in the communication, as we choose to send some emails from Notifications and some from Workflow.

salmdo · ‎09-08-2020

Hi, I see we have a new feature with workflow calls Workflow Task and we can push the JSON input, it's so helpful but if we would like to use JSON object is like a configuration and if we have many workflows call to this workflow then we need to add it to each of them. I see we have "Use default" for the text type so it's so powerful if we have this option with JSON type. Thanks

pask · ‎06-03-2020

Hi, we are getting error in Zuora Workflow when we try to download a file from sftp using * as search string when no file is found. Is there a way to get a checkbox in order to not trigger the error? it will be better to let the user decide to stop the task when no file is found. Thanks in advance Pasquale

msonsma · ‎05-28-2020

Liquid runtime can be extended with custom filters / tags extension written in Ruby. For instance Shopify adds a lot of extension on top of the standard runtime. The same it true in the Zuora Workflow's Liquid runtime: the regex filter is a custom filter extension written by Zuora and added to the workflows Liquid runtime. Benefits of writing custom extensions: - Writing complex algo is easier in ruby than in plain Liquid. - Better error / exception handling in Ruby - Utilize the functionality of existing Ruby classes ( why reinvent the wheel ) - Implement beter filter / tags: for instance the above mentioned Zuora regex filter only implement limit set of options of the underlying Ruby regex class. By writing your own you utilize the full power of the regex class or any other.. - Re-useable code library: by writing extensions you can use them in all workflow tasks ( you do not have to copy and clone the code ) The option to define custom extension should be available on the both global level as on workflow instance level and should ofcourse be exported/imported when the workflow is exported/imported. Just think about it...

Happy Business Starts Here

Vision

Products

Zuora Central Platform

Products

Zuora Marketplace

Solutions

By Industry

By Role

Customers

Resources

Resources

Subscribed

Support

Company

Workflow Ideas

Display Workflow Triggers in Workflow List

Workflow editor: Option to open the payload browser in a task configuration pane

Option to define create a library of tasks templates

REST API to rename Workflows

Option to apply changes made in instance task config to the workflow task config

Option to protect a workflow from being (partially) copied

Update existing Workflow by JSON Import

Using external smtp server for sending emails through workflow

Access to Run Number as a Workflow Data item

Shared Memory between Start and on Finish Workflow task

XML transform task does not allow to produce true text or csv file

Rest API to Update Workflow object

Liquid Tester Enhancement

Data Query wrapper sync mode

Advanced workflow parameter set

Searching through Workflows through a specific field processed in it

Show emails sent from the Account screen

Workflow Task - Use default value with JSON input

Error in SFTP Download when no file is found

Option to extend the Workflow's Liquid runtime with custom filters and tags extensions.

Advanced search function inside workflow history

Ability to add HTML invoicing templates