Hi @roklde I did check, but there was no documentation folder included. @anmise thanks, I got it.
Hi Charith Do you mean a sync job in Monitor Schedules on FSM side? If so, yes, I have a job setup to sync every two minutes. Here is an example:<perform_batch> <perform_send_rota_data_to_dse> <parameters> <dataset_id>DATASET_ID</dataset_id> </parameters> </perform_send_rota_data_to_dse></perform_batch> I have this set up for all datasets. Any idea what else it could be?
Hi KaiThanks
Hi Kai, Thank you. How do I contact the FSM team specifically? Must I repost this issue in a different sub-forum? Regards,Hannes
Problem with tasks changing status from Allocated to Unallocated even with Resource availability and active SLA’s, has been resolved.A PSO parameter was changed; the HTM is an older version that needs to be upgraded. This was causing intermittent glitches until it was the parameter was changed to Straight line. PSO Parameter was changed - TravelCalculationOption change from HierarchicalTravelMatrix to StraightLine
Thanks for the reply. The reason it gives is : Reason: The current plan does not schedule this activity. This does not make sense as there is ample space in the schedule to schedule the task: The tasks also come through as allocated, and is then changed to unallocated shortly after.
Hi, thanks for the replies everyone. @ishD Can you maybe give me a bit more info about how you went about making this change e.g. business rules used, which XML Maps were affected, where a good starting point would be for this change etc.
Hi I did manage to fix this issue by marking all datasets as inactive in FSM, refreshing cache, marking them all active again, refreshing cache and reinitializing. When refreshing PSO, the datasets were set to Active again.
It is integrated with FSM. I have checked that the ThreesixtyDataset_ID are all active, and in the Scheduling app params that Threesixty_enabled is marked as “Y”.Any idea where else I could check, or what might have caused it?
Hi @Sajith Anushan Thank you for the reply, this answers my question. Regards,Hannes
Hi @Kalpa Perera What I mean with Resource ID was changed, is that the the Scheduling Resource flag on the user profile was unchecked and checked again. The user was then assigned a new resource ID/number. The resource was then added to the team using the new resource ID (767), but the old resource ID (507) was not deleted from the team. The cache was refreshed, and the dataset initialized in the Scheduling Manager in FSM. The resource then showed up in PSO, and was available under 507 and 767 in the Resources tab and the Resource Planner, and was then added to the planner. I know I can go delete the old resource from the team in FSM and PSO and it will disappear. I just want to know if there is some sort of safeguard to prevent this type of duplication happening as in the example above, or will the responsibility be on the user doing the team setups to manually ensure that this type of duplication does not happen? Regards,Hannes
Hi Managed to fix this error by switching on a parameter in PSO under Administration (the ScheduleCommittedActivitiesInActiveShift parameter was switched off). After this change no more problems with tasks being moved to the end of the rota period. Regards,Hannes
Hi Have managed to fix this issue by clearing the THREESIXTY_RESOURCE and THREESIXTY_RAM_LOAD_HISTORY tables, unchecking all Schedule Resource flags on users, and re-adding them as Resources. After initializing the dataset the resources started populating correctly with new ID’s. Regards,Hannes
@AdrianEgley Ok, I have checked the input history folder, and it seems that the items are getting created (tasks, scheduling resources etc.). When doing a test, a task was created and showed up as allocated on PSO, until it got committed/assigned to a resource (who is a resource on the team in FSM, but not on PSO). The task then disappeared from PSO. I also sometimes get an exception message when initializing the dataset:<perform_initialize_threesixty_result><result type="Exception"><error><application_error><severity>ERROR</severity><message>Input Reference ID already exists: INIT_2021_6_18_15_12_26</message></application_error></error></result></perform_initialize_threesixty_result> Regards,Hannes
Hi @AdrianEgley Fields listed under the EXPORT_TASK_UPDATE_COLUMN_CHANGED are: TASK_TYPE,ADDRESS_ID,PRIORITY,SPLIT_ALLOWED,MIN_SPLIT,INTERRUPT,COST_OF_SPLIT,DESCRIPTION,CREATED_DTTM,SCHED_REF_ID,SCHEDULE_VALUE,SCHED_TASK_DUR_MIN,PLAN_TASK_DUR_MIN,TASK_STATUS,USER_DEF16. I have tried updating the Scheduling App Params (EXPORT_TASK_UPDATE_COLUMN_CHANGED, EXPORT_TASK_TEAMS, EXPORT_TASK_TYPES, EXPORT_TASK_STATUSES_TO_EXCLUDE etc.) but still not getting any data to push to PSO. Regards,Hannes
Hi @Vinu Peiris Sorry for the previous screenshot. Here it is larger: I don’t think I can grab a screenshot now of when it stops working, as this stopped working, but I don’t know exactly when it stopped working. Regards,Hannes
Hi @Vinu Peiris I have checked the event log and it seems the SQM is running:Should I provide system_events log file?Regards,Hannes
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
