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 14 Next »

Overview

This page aims to provide a comprehensive overview of the necessity to review and optimise existing Salesforce flows within Jarvis. Additionally, it aims to establish best practices for creating and maintaining flows to ensure efficiency, reliability, and scalability.

The scope of this work includes Workflows and any processes in the soon to be retired Process Builder.

Table of Contents

What’s the Problem?

Flow Proliferation

Jarvis currently hosts over 250 active flows within the Salesforce environment. Unfortunately, many of these flows lack proper documentation, leading to challenges in understanding their functionality, dependencies, and potential risks.

We don't have a way to export this macro.

Impact of Undocumented Flows

  1. Error Occurrences: Undocumented flows contribute to increased error rates as changes are made without a clear understanding of their interconnectedness.

  2. Knowledge Gaps: Lack of documentation hinders the transfer of knowledge between team members, making it difficult to troubleshoot and resolve issues efficiently.

  3. Maintenance Challenges: Updates and modifications become cumbersome, leading to potential system instability and delays in adapting to business changes.

Why do we need to review Flows?

Risk Mitigation

  1. Error Reduction: Documenting existing flows allows for a comprehensive review, identifying potential sources of errors and mitigating risks.

  2. Enhanced Maintenance: Reviewing and documenting flows simplifies ongoing maintenance, ensuring the system remains agile and adaptable to changing business needs.

Increased Collaboration

  1. Knowledge Sharing: Proper documentation facilitates knowledge sharing among team members, enabling collaborative problem-solving and reducing dependencies on individual expertise.

  2. Cross-Functional Understanding: Well-documented flows enhance communication and understanding between different departments, fostering a more integrated and efficient working environment.

How are we approaching this challenge/technical debt?

  • We will:

    • Build a consensus about what the problem is and the need to take action to address it.

    • Standardize, simplify and reduce the number of flows across the Org

Flow 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

Appendix

Business Area

Number of Flows

1

TAP

131

2

WB

60

3

Hogwarts

45

4

ASOP

13

5

All

250

  • No labels