Having trouble sending data from multiple data sources to create single merged document? Need to delay a merge until you have all of the data? Or want to create a little workflow in your process? Great news! We have a feature called “Sessions” and it is ready for you to explore.
How do the sessions work?
In a nutshell, instead of merging the data right when you send it to us, we save it (encrypted) for later. You can continue to send more data and it will save that data as well. Then when you are ready to merge, it takes uses all of the data you sent over time for that session.
An example scenario where sessions can be used
Let’s say you are in the construction business and you use a CRM to keep track of all your projects, managers, buildings, etc (we’ll call these “objects”). Before, if you wanted to generate a contract, you’d have to pick one of your objects, send the data over to WebMerge and then manually enter any missing information. Now, you’ll be able to send data from any of your objects and have it go to the same spot. In other words, you could send the building information over, then send the project manager’s information over and it will have both sets of information ready for you to merge.
How do I use sessions?
Using a session is very easy. We keep track of each session using a unique key (name, email address, etc) that you choose/define and all you need to do is pass that key in your Merge URL for the document.
When we detect the “session” parameter in the Merge URL, we look for a session that already exists and save the new data (if you send data that already exists in the session, we will use the newest data we receive). If a session with that key does not exist, then we create a new session. Each session is unique to the specific document you are merging (ie you can use the same key for a different document and it will create a different session).
When you are ready for the data to be merged, you can add a “session_merge=1” parameter to the Merge URL and that will tell our system to merge the session.
After a session has been merged, we delete the session and data from our system.
Can I use sessions for Data Routing?
Yes! It works exactly the same for your data routes as well. Simply add the session parameters to your Merge URL and it will save the session.
I use a service that doesn’t allow me to modify the Merge URL
No problem, what you’ll need to do is use the following custom fields in that service or define them as variables in your document settings so they show up in your field list.
You can use the Field Map to add the fields, like this: