Skip to main content

Hello,

we need a solution to efficiently manage exceptions in the calendar for team meetings without the need for a manual import per technician. This solution should take into account both existing and future exceptions in reports.

The question now is in which tables the recurring calendar exceptions entered in PSO are stored. Here we can examine in more detail what the solution idea is and how it can be implemented.

 

Thank you

 

Best regards

Markus

 

Hi Markus,

Please an idea in the community and we will get the product team to consider this.

Thanks,

Reece

Dear Product Team,

 

I am writing to present an area of our FSM and PSO systems that requires your attention and expertise.

 

Currently, the FSM and PSO systems are equipped to synchronise calendar exceptions between both systems. These exceptions are manually set up for individual technicians in either of the two systems, which then automatically get reflected in the other. While this process works fine for small-scale exceptions, when it comes to larger volumes or longer durations, the process becomes tedious. The import functionality offers a potential solution for this issue; however, it comes with the drawback of requiring any changes to be manually updated, a process that can be very time-consuming.

 

The PSO system offers an advantage in the form of recurring calendar exceptions. This feature enables users to set up a single exception that can recur weekly for an extended period. Any adjustments to these exceptions can be made with ease. However, this process requires some fine-tuning as there are two ways to modify these recurring exceptions:

 

  1. Simply changing the day and/or time of the exception.
  2. Ending the current recurring exception and creating a new one with the adjusted date.

 

In principle, this feature addresses the issues with calendar exceptions quite effectively. However, upon its implementation, a major discrepancy was discovered. While the recurring exceptions work perfectly in the PSO system, they are not properly reflected in the FSM system, and more importantly, they are not taken into account in the analysis reports. To address these concerns, I kindly request your team to investigate the following:

 

  1. Ensure that the recurring calendar exceptions from the PSO system are correctly synchronised and individually visible in the FSM system.
  2. Validate that these recurring calendar exceptions are accurately considered in the analysis reports, which currently do not include them.

 

The objective is to make the process user-friendly and straightforward while ensuring that the data captured in the system is correctly reflected in the reports.

 

If you require any additional information or would like to set up a meeting to discuss this further, please do not hesitate to contact me.

Hello,

 

any answer from the product team?

 

Thanks

regards

Markus

Reply


Terms & ConditionsCookie settings