Any potential issues with disabling "Process Expense Allocation" scheduled job?

[PaulaaO]

Hi Community,

We have been asked by a client to disable the scheduled job that updates the State field for expense lines from "Pending" to "Processed" as they wish to handle this manually.

I found the scheduled job -> Process Expense Allocation which references this Script Include: "ExpenseAllocator", but I am a bit unsure if turning off the scheduled job is likely to have adverse effects, especially as I noticed it's an OOTB component which is also Active by default. I was unable to find any official documentation or other posts related to this.

Thank you in advance.

Paula

[Bhuvan · Accepted solution]

@PaulaaO 

Based on the Scheduled Job and Script Includes definition, it should not have impact to any other functionality.

I would recommend to test it by disabling the scheduled job in development environment first to make sure it does not impact any of the functionalities and implement it in other environments accordingly.

If this helped to answer your query, please mark it helpful & accept the solution. 

Thanks,

Bhuvan

[PaulaaO]

Hi @Bhuvan   many thanks for your input. Could I please ask what exactly should I check after disabling the scheduled job, to ensure it doesn't impact anything else? Thank you 🙂

[Bhuvan]

@PaulaaO 

As per Scheduled Job and Script Include definition, disabling it should only stop updates for expense lines that are in Pending state. You can randomly test other state changes or scenarios and make sure behavior is working as expected.

If this helped to answer your query, please mark it helpful & accept the solution. 

Thanks,

Bhuvan

[PaulaaO]

For completion

Given it's an OOTB component which is active by default, to avoid too much technical debt it was agreed to disable the scheduled job and create a copy of it where customisations will be applied to satisfy the requirements (I missed to mention in my original post that we only want the project expense lines to not move to Processed)