- Mark as New
- Follow
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report
You can hack mirror page for SMS by editing the delivery content and force the use of mirror page.
But be carefull: depending the way you build the mirrorPage, you can have performance issue:
nms.delivery.GetMirrorURL() should not be used for a non unitary used: it creates SQL request in the database to retrieve the delivery midRemoteId each time.
you should then prefer the undocumented feature escapeUrl(simpleRevCrypt(@midRemoteId, @broadlogId)
In order to have an idea about the difference between both way:
getMirrorURL() => 16 mirrorPages URL generated per second
escapeUrl(simpleRevCrypt(@midRemoteId, @broadlogId) => 1200 mirrorPages URL generated per second
If you're using Message Center with getMirrorUrl() this is even worse: 4 mirrorPage URL generated per second (the function is using a soap call to the RT instance)...
For hacking this and having the same performance as the other, ther's a tricky hack but it wasn't me that coded it and I would have to redo this with MC... I would perhaps prefer to extend rtEvent Schema and store the mirror page URL in it by changing the ootb workflow & js to retrieve the rtEvents
In case, carefull also when you'll generate PDF using the created URLs as, depending the volumetrie, it can badly affect the webserver process
Views
Replies
Total Likes