Workflow Ideas

govindrawat · ‎04-28-2021

What problem is the idea trying to solve? With the latest release update, currently there is no read-only workflow access hence anyone who has workflow access is able to read, write and execute the workflow. This is challenging in cases where teams who want to view or review a deployed workflow for analysis, triage or any other reason, can't do so as they might be from the group which doesn't have deployment ownership. If the idea is implemented how would you use it? Since only deployment/support team needs to have the write/execute access, any other team which needs to refer to the workflows (dev or sanity teams) cannot do so. There should be finer controls like read, write and execute for workflows controlled via roles so each team can be provided appropriate access. Current Solution What is your current solution (if any), and why is it not great or viable? We are currently providing only selected people from each team the write access in non-prod. The operations/deployment team has to take the additional toil of view/review/triage/analyze etc. in prod due to absence of read workflow role. With the proposed idea, workflow access can be streamlined without compromising environment sanctity.

msonsma · ‎04-08-2021

Case: When uploading a (huge) file to an SFTP server, there is a possibility that the file is already picked up by a server side process before all data is uploaded. Some server processes implement safe guards by the waiting for the file size to stabilize; other server processes require atomic file creation to be implemented by the client side. Current situation: The Workflow's SFTP::Upload taks does NOT have support for atomic file creation making uploading files to a server that requires atomic a tricky and error prone action that can lead to various race conditions and erratic behavior in production environment and are hard to detect in the a workflow. For uploading financial files this is basically a NO-GO. Change requested ( read required) The Workflow's SFTP::Upload task should implement support for atomic file creation: Atomic file creation can either be implemented in two ways: Uploading the file with a temporary filename extension first and rename it ( = atomic action ) to the correct extension after the data is uploaded. Upload the file in temporary folder first and than move/rename ( = atomic action) to the correct destination folder. The SFTP::upload task should implement both options as not all FTP server support cross folder renaming. The task should have two additional fields: one to define an optional temporary file name extension and one to define an optional intermediate upload folder. Another and better option is to introduce a new SFTP::FileFolderAction task that implements (S)FTP file and folder actions: rename, delete, move, create folder, remove folder, list folder. This provides more flexibility. Manfred Subscriptionfactory.com

pask · ‎02-16-2021

Hi, we are experiencing errors in rerunning failed custom object record create tasks in Zuora Workflow. When we re-execute we got all custom object records duplicated. E.g. We have a callout with 500 total insert, Task fails on 2 records only. When we resubmit the request Zuora will write once again all 500 records. so in custom object we have 998 records instead of 500. Could you implement a partial retry in order to avoid this problem? Thanks in advace Pasquale

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

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 )

pask · ‎10-16-2019

Hi, we have some flows that uses AQUA API to get data. It would be useful to enable AQUA query to support Custom Objects, in order to leave the logic unchaged in quering custom objects and Standard Objects pre-joined. Thanks in advance.

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.

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

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 ?"

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.

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

ASchwarz · ‎11-20-2018

As we are using the advanced invoice settlement feature and have several templates for invoices, credit memos and debit memos we need to be able to update this within a workflow. At the moment we are only able to export and update the invoice template ID for accounts.

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

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

mike-reid · ‎03-26-2019

Support for the Files object — such as uploading a CSV —has been such a welcomed addition to Zuora Workflow! As we branch out, looking to automate more of our Workflows, we hit a hurdle. We cannot trigger a Workflow remotely (via API) if it requires a Files object to be uploaded (e.g. CSV file), yet uploading a CSV is definitely supported via the Workflow UI. Triggering via API is great, and I've been successful doing so from Postman, etc, but I am hoping we can extend support for File uploads in order to remotely trigger Workflows that require a Files object as input. Postman supports this, but I was not satisfy on Zuora's end without this error: Status: 406 Not Acceptable NOTE: This is a cross-post from the Zuora Workflow board (and accidental posting on the Reporting Ideas board), per the recommendation from the Zuora SME team: https://community.zuora.com/t5/Workflow/Triggering-Workflows-Leveraging-File-Uploads-CSV-via-API/gpm-p/27694#M27

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

Finer Workflow Access

(S)FTP Upload - Atomic File Creation support

Partial Retry on Custom Object Create REST-API via Workflow task

Display Workflow Triggers in Workflow List

Option to define create a library of tasks templates

REST API to rename Workflows

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

Option to protect a workflow from being (partially) copied

Query Custom Objects using AQUA API

Update existing Workflow by JSON Import

Error in SFTP Download when no file is found

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

Shared Memory between Start and on Finish Workflow task

Using external smtp server for sending emails through workflow

Access to Run Number as a Workflow Data item

Update Credit Memo/Debit Memo Template ID via Workflow

Tool For Import/Export Workflow

Advanced search function inside workflow history

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

Add File Upload (CSV) Support for Workflows Triggered via API

Using external smtp server for sending emails through workflow

REST API to rename Workflows

Access to Run Number as a Workflow Data item