Attention: Confluence is not suitable for the storage of highly confidential data. Please ensure that any data classified as Highly Protected is stored using a more secure platform.
If you have any questions, please refer to the University's data classification guide or contact ict.askcyber@sydney.edu.au
Skip to end of banner
Go to start of banner

Jarvis Salesforce Flows Review

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 11 Next »

Scope includes Workflows and Process Builders

Why the need to review Flows?

  • There are currently > 250 active flows in the Jarvis Org

Here are some high level stats:

Area

#

1

TAP

131 (18)

2

WB

60 ()

3

Hogwarts

45

4

ASOP

13 ()

5

All

250

Real life examples:

Add link to tickets if that is easy

How are we approaching this challenge/technical debt?

  • We will work to build a consensus about what the problem is and the need to take action to address it.

  • We will standardize, simplify and reduce the number of flows across the Org

Best practices to consider:

2-3 Flows per Object. No More

Guiding principles:

Link to the page Yeng has created

Troubleshooting of Flows:

  • USYD Error Log for the recent Flows

What is(are) the proposed solution incl ways of working?

(Swathi)

How many flows do we think we need to optimise?

What are the steps we need to take to start to address the issue:

Dependencies

  • No labels