Workflow Ideas

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

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 )

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...

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.

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 · ‎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...

chiragjha · ‎05-25-2020

Hi, When i run below code in liquide sandbox (https://jumpseller.com/support/liquid-sandbox/) its working fine. ------------------ {% assign ChkCrrTotUsg = 1000 %} {% assign FetchTotUsg = 2600 %} {% if ChkCrrTotUsg == 0 and FetchTotUsg > 1000 %} {% assign cTotalUsage = FetchTotUsg | minus: 1000 %} {% else %} {% assign cTotalUsage = ChkCrrTotUsg | plus: FetchTotUsg %} {% endif %} {{ChkCrrTotUsg} ---------------------- But when i try to run it in workflow "logic-if" it keeps throwing following error. [ If statement evaluated to ''. Only 'True' and 'False' are acceptable evaluations.] I think its some simple mistake i am doing, but hard for me to figure it out in workflow. Thanx, Chirag

pask · ‎05-07-2020

Hi, could you enable Zuora Workflow File::CreateCsv in order to support constant values in csv creation? For example we would like to create a csv with an additional column that is a constant value. It could also be useful to make the task non positional and add the ability to put some liquid code and multiple fields concatenation in order to extend data export functionality. Thanks in advance

pask · ‎05-07-2020

Hi. We need to produce a positional txt file. We would like to use Data Query Workflow Task. Could we find a way to eliminate header from output csv? Is the only problem we have in this implementation, maybe a checkbox in data query task. Thanks in advance Pasquale

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

Cor · ‎01-10-2020

Hi, To increase the use-cases that can be covered by the approval task i would like to see the following: 1. Being able to add a note to the approval task that is displayed with the Task in the Collections Window so the approver can be provided with addtional information on what they need to approve for.Currently only the following information is provided along with the approval taks. With this functionality you could for exmaple achieve the following: e.g. we could create a workflow which is triggered in Credit Memo creation. In the notes we could than provide the Account, TCV, Credit memo amount and number, original invoice amount etc. so the decision can be made on the same screen. 2. Have the pending approval task send as an email so the approver is aware of it without going to the Collections Window. ideally with the notes mentioned in point 1. This email should have a Approve & Decline link so the task can be approve directly. This might also avoid the need for Collection window, by direclty approving the task in 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, A tool for importing and exporting workflows. This tool should: 1) Export All Workflows or a Subset of Workflows 2) Import a Subset of Workflows. Note 1: when importing a workflow having the name matching with a preexisting one it should autorename the old one in order to track the old workflow history and import the new one. Note 2: We usually use Workflow Name instead of the id for portability reasons and if we try to import a workflow using the same name all callout goes KO. Note 3: We tried to develop a tool in java but we can't perform workflow name update using API we can only perform get all workflow and create workflow task. Thanks in advance. Pasquale

pask · ‎10-08-2019

In order to perform a fast and correct bug fix we need to be able to search inside all workflow history for a specific key, contained for example in the input parameters or inside any block in task execution. Thanks in advance Pasquale

ASchwarz · ‎09-16-2019

For customers who want to receive their invoice via post there is a possibility to download the invoice pdfs in Zuora in the export. This is missing for credit and debit memos. I tried to create a workflow and used the API to get the files. https://www.zuora.com/developer/api-reference/#tag/Get-Files This works fine but the problem is, that the workflow is not able to actually download the pdf but instead is throwing an error. When I use the API request with postman I can easily download the files. This functionality should work also within the workflow to provide the pdfs of Credit and Debit Memos automatically.

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

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

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

Option to protect a workflow from being (partially) copied

Option to define create a library of tasks templates

Update existing Workflow by JSON Import

Using external smtp server for sending emails through workflow

Shared Memory between Start and on Finish Workflow task

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

Error in SFTP Download when no file is found

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

Debug Workflow liquid syntax

CSVCreator Enhanced Task

Remove Headers from DataQuery to Create Positional Files Using DataQueries

REST API to rename Workflows

Enhance the Approval Task

Access to Run Number as a Workflow Data item

Tool For Import/Export Workflow

Advanced search function inside workflow history

Download of CM/DM Templates via Workflow or via exports

Ability to add HTML invoicing templates