Overview
To address the issues encountered in mobile terminal integration, you can refer to the troubleshooting manual to quickly find and resolve relevant problems. For details, see: Mobile Terminal Functions FAQ and OA Error Code Comparison Table.
Solution
When encountering integration issues on mobile terminal, you can first troubleshoot them according to the following process.
For details about debugging tools, see Debugging Tool for Mobile Terminal Integration.
Checking Each Function
If you cannot resolve problems according to the process, you can troubleshoot and solve them according to specific issues and functions.
Application Management–Server Address
Problem:
Deployment accesses error, unable to load.
Solution:
Server address cannot end with /, mainly because it will affect the generation of link concatenation parameters and the generation of scheduled push link.
You can modify the SSO link or platform access address to avoid this issue. The server address should end with /decision and should not only be written as http(s)://domain:port.
Plugin Registration
Problem:
When you update the lic of expired plugins, it remains shown as not registered on the interface,
Solution:
1. Confirm whether the plugin is used for second development.
2. Test in multiple environments to confirm whether the lic is abnormal (Abnormalities in FanRuan Market may cause functional exceptions in the applied lic.).
Personnel Management
Problem:
Click Personnel Management, and it will prompt error 500.
Solution:
Check if there are multiple versions of integrated plugins in the folder plugins, close the project and delete the extra plugins. Keep the needed versions and restart the project.
Single Sign-on Login Failure
Solution:
For details, see Troubleshooting Steps for Failing to Single Sign-on.
Receiving Message
1. Users Cannot Receive Messages
Solution:
a. Manually sync users again.
b. Check whether the information of the user is matched with a platform user.
c. Check whether the matched platform user is within the scope of message push.
2. A User Cannot Receive Messages
Solution:
a. Check whether it is a user added by multiple enterprises. If so, the user needs to update plugins to V 11.0.62 to cope with issues due to name repeating in multiple enterprises.
b. Check whether the user can be found in the synchronized address book.
c. Check whether the information of the user is matched with a platform user.
d. Check whether the matched platform user is within the scope of message push.
Message Content
1. Message content with Word Limit
Solution:
Text message: Message content, up to 2,048 bytes, will be truncated if exceeded.
Graphic message: Title, not exceeding 128 bytes, and description, not exceeding 512 bytes.
2. Cannot Find Template File
Solution:
a. Check whether there are any files generated in webroot/WEB-INF/schedule/task_name/time/corresponding_folder.
b. Confirm whether there are two environments configured with the same application, which is not supported on mobile terminal, leading to conflicts except integration on two sub-nodes of a cluster.
c. Confirm whether there is cluster environment. If so, check whether the data between the two nodes are not synchronized, resulting in accessing the unsynchronized data node.
3. Problems in Displaying Content
Solution:
Update the new adaptive plugin for problems in displaying the scheduled results in H5.
4. Message Push not Based on Assigned Permissions
Troubleshooting steps:
Check whether there are other synchronization events, ETL extractions, or events affecting the synchronization during message push.
Parameter Cannot Taking Effect
Problem:
Set parameters now() and fine_username in generated SSO template link, but they do not take effect.
Troubleshooting steps:
In Task Schedule, if the setting of parameter fine_username is ineffective, document widgets may be not available.
Images and Text Push
1. Does Not Display the Cover Image Occasionally
Troubleshooting steps:
a. . Confirm whether it is a cluster environment.
b. If it is a cluster environment, check whether each node of the cluster is normal, whether the status server and file server are configured, and whether the file cache is enabled.
2. Unable to Receive Image Push
Troubleshooting steps:
a. Check if the task is configured with images.
b. Try to upload the images again.
