10,730
edits
(→Questionnaire: Script Path default value) |
|||
Line 1,446: | Line 1,446: | ||
return true; | return true; | ||
}, true, null); </syntaxhighlight> | }, true, null); </syntaxhighlight> | ||
== Route plan == | |||
You can use HTML and JavaScript to extend [[route plan]] beyond its out-of-the-box functionality. The following events can be handled: | |||
* Item Added - receiving added entity | |||
* Item Removed - receiving removed entity | |||
* Item Completed - receiving entity to be completed and status to be set | |||
* Item Saved - receiving entity before it is saved | |||
* Item PostSaved - receiving entity after it is saved | |||
* Route Saved - receiving all entities in the Route before they will be saved (user clicked on Save button or other internal trigger). It must be possible to determine which entities are dirty and thus will be saved and which not. | |||
* Route PostSaved - receiving all entities in the Route after they were saved. | |||
* Route Reloaded - triggered every time the records in route are reloaded, e.g. in case they are reordered, added, removed, completed or optimized. Receiving all entities and additional info such as route day. | |||
You can find information and examples on our [https://github.com/Resconet/JSBridge/wiki/MobileCRM.UI.RoutePlan Resco GitHub]. | |||
== UI (Home) replacement == | == UI (Home) replacement == |