Timing is Everything in Fusion Lifecycle
The phrase “Timing is everything” holds true when it comes to Cloud Applications. Many people don’t understand the reasoning behind “Timing Out” in Fusion Lifecycle. Customers and users have brought to my attention that many actions relating to loading, importing, and scripting at times get “TIME OUT”. To better understand and explain the issue at hand, we need to break them down into 3 categories.
- Workspace Loading
- Data Importing
- Performing Action Script
Many factors can potentially effect the loading of the workspace. For example the network, browser, server, and amount of data transfer.
I recommend some tips and tricks to help minimize the impact and hopefully speed up workspace load time.
Cut down on the number of images that are being displayed in the workspaces. The more images in the workspace, the more time it will take to load.
Try to utilize more of the “Collapse Section Feature” in many of the workspaces. When you have a huge amount of fields (100 + fields) in a workspace, it will require some data transfer time. By collapsing the non-essential sections it will reduce loading time.
The number of records and number of fields in a record play a factor in the length and time the system takes to import. When the system imports 1000 records and each record has 100 fields, consider the amount of data the system has to process. My recommendation is to cut down on the number of records imported based on the number of fields with each record. Also consider importing data during after hours rather than during business hours.
The number of relationships and dependencies will impact the importing time, which may possibly lead to “Timing Out” or “Pending”. When you import 1000 records and set the hierarchy to 5 levels deep, the system will require more computing and processing time.
For this, I recommend using less records on import and/or using REST API for complex BOM Structure.
Many times action scripts time out because it exceeds the 9 sec limit. The operation takes too long trying to perform too many tasks. I recommend separating the number of operations from one source to multiple sources by utilizing Script on Create, Script on Demand, and Workflow Action Script. By interconnecting the scripts and triggering through a series, it will run longer. Example: Create Auto Number Sequence by using Script on Create; Next, utilize Workflow Action Script to create and pre-populate Milestones; Finally, Spawn New records by utilizing Script on Demand.
The use of functions calling other functions helps the Administrator avoid re-writing redundant codes. By utilizing library, it helps the Admin save time re-writing the most frequently use codes. However, if the Admin begins to create library code with a string of functions calling other functions in other libraries, at the time it will contribute to the “Time Out” issue. When you have too many embedded or daisy chained functions, it will require the system to allocate time to find all the functions and organize based on the sequences, and then execute the script. There are many times the script will only run half way because the calling of the functions may take 3 secs and 6 secs to execute a massive operations. Here, I recommend cutting down on creating too many unnecessary functions in a library. Also cut down on the number of functions calling other functions in other libraries.