Merging codes in RecMan
Introduction - mScript
mScript is the name of the system we use to merge information into templates. Quite simply, it will retrieve information automatically without you having to enter it manually. Both employee agreements, order confirmations and offers are all good examples of areas of use for mScript. The merge codes streamline the workflow and fill in information specific to the application area.
How to use mScripts
mScripts are built using a combination of two parts. The main object you refer to and the information you want from this object.
Some can only be used in the email, some can only be used in the text part, and some can be used in both places.
See the section on global and non-global mScripts further down for more information on this.
Structure of mScripts
When using mScripts, placement is important. The object is always on the left and has an @ in front of it. Like this user object, which points to the logged-in user (you):
@user
But to get information from this RecMan user, you need to add what information you want to retrieve.
Below we refer to the user's name:
@user.firstName @user.lastName
As you can see, the object and the information are separated by a period. And the data is written with the first letter in lowercase.
mScript examples
------
----------
---
------------------
------------
-----
@user.firstName @user.lastName
@user.email
@corporation.logo
Hi @candidate.firstName,
Here is the order confirmation for the job @job.name. Take a look and sign it when possible.
First day at work: @job.fromDate
Last day at work: @job.toDate
In the table you will find the salary overview for the job:
@job.calculationTableSalary
Your contact person at work is:
@companyContact.name
@companyContact.email
@companyContact.mobilePhone
Attendance is on Tuesday at the address:
@companyVisitAddress.address1
@companyVisitAddress.city
@companyVisitAddress.postalCode
Global and non-global mScripts
Some mScripts can be used anywhere in RecMan, while some can only be used in certain places.
Example:
@user is a global mScript that can be used everywhere.
@project or @job are mScripts that cannot.
This difference is because @user can retrieve the user information of the logged-in user, regardless of where you are in the system.
While @project needs a connection to the project to get the information from it, so if you send an appointment to the candidate from the candidate card, it doesn't know which project to choose and therefore does nothing.
Always consider what kind of information is available and where you are sending it from.
Testing mScripts before use
In many places where you enter a text - for example, when you create an agreement - it is possible to test the mScript that has been entered. This makes it possible to see whether it actually works and retrieves correct data before, for example, the agreement is sent off.
When you add a template or write text where you have added mScripts, you can click on the lightning symbol in the top right. This will automatically populate the mScripts with the information stored in the reference fields.
Here is an example of how this works:
Get started with mScript
Take a look at the overview of all our mScripts and find the ones that suit your needs!