Skip to main content

Hi Experts,

When a technician adds their signature from a mobile device, it is saved in the mobile database as a negative value by default. This value is then sent to the FSM server, which identifies the negative value and converts it to the correct ID based on the sequence of `tech_signature_id`. This process is handled on the server side. As shown in the attached image, all `tech_signature_id`s created on mobile devices are negative values. This helps avoid mistakes when many technicians are working simultaneously.

Tech signature id before syncing with the server.

However, my problem is that on the server side, the `tech_signature_id` is not being converted to a positive value after the data comes from the mobile device.

task.tech_signature_id in web client

This issue does not occur every time. I had to create at least 10 tasks to reproduce it. The current environment is UPD23, and I tested this on an Android device. I also initialized the UPD23 server into the UPD28 Android and Windows applications, where I was able to recreate the issue.

I believe the issue might be a server side product bug. But are there any configuration items I can check to address this problem?

 

Note: The customer is using baseline mobile applications, and no server customizations have been made to the task policies.

 

Thank you!

Hi @Chethana 

This problem was also present in version 2.25 of iOS. Please check this ticket.

 

https://support.ifs.com/csm?id=csm_ticket&table=sn_customerservice_case&sys_id=eac7d60edbf43150f38822e50596191d&view=csp


R&D mentioned that they fixed this issue in version 2.27.

I investigated the mobile code. The mobile code does not send a value for the task.tech_signature_id column. Mobile usually generates negative values. The server generates a positive value after the process sync message.

If it is not generated, then the problem is with the server. Check if any business rules work for this task.tech_signature_id column.

 

 

Reply


Terms & ConditionsCookie settings