
Trial Period Evaluation: Tailor the Form, Fill It in MSS, Automate It with a Scheme
The trial period of a new employee is a moment of decision for both the employee and the company. Under the Turkish Labor Law it lasts at most two months, or up to four months with a collective agreement; before it ends, the manager has to evaluate the employee and the evaluation has to be recorded.
In practice this is often a Word form sent by e-mail: managers forget it and the period quietly runs out. In this post we cover three steps in OrchestraHCM:
- Tailoring the trial form to your company
- Filling in the form as a manager in MSS
- Running reminders periodically with a scheme and the JOB function
For an overview of the module, see the Probation Period module page.
1. Tailoring the Trial Form to Your Company
HR manages the questions of the form on the Trial Period > Trial Form Design screen. As long as your company has no catalog of its own, the system uses the default form. It has three sections:
- Compliance with Rules: commitment to the workplace rules and business ethics
- Success Criteria: meeting the requirements of the job, the required qualifications, openness to development and whether anything prevents the continuation of the contract
- General Evaluation: the manager's overall opinion
As soon as you edit and save the default form, your company gets its own catalog. The screen has three tabs:
- Sections and Questions: add sections and questions, reorder them, make them required or inactive. The order on the screen is the order on the form.
- Answer Scales: define the options of choice questions. Yes / Partly / No, Yes / No and a 5-to-1 Expectation Rating come ready. A scale can be used by several questions and several forms.
- Preview: see the form as the manager will see it, without saving.
Question Types
| Answer type | What it does | Example |
|---|---|---|
| Choice only | The evaluator picks an option. | Yes / No questions |
| Choice and comment | A comment can be written next to the option; the comment can be made required for certain options. | "Is there anything that prevents the continuation of the employment contract?": comment required when Yes is chosen |
| Comment only | Free text. | General evaluation |
More Than One Form
One form may not fit every position: you may want separate forms for field staff and office staff. Start from scratch with New form, or duplicate an existing form with Copy form and change it. When there is more than one active form, the evaluator chooses the form on the screen; with a single active form the choice does not appear at all.
Good to Know
- The question code is a key. Answers are saved to the trial form infotype (0503) by this code. Saved forms keep their own question texts, so changing or deleting a question later does not break past evaluations.
- Multilingual texts: texts are saved in the language you are logged in with. To translate, log in in English and enter the texts on the same screen; untranslated texts appear faded.
- Load defaults: replaces the catalog with the default form; the database does not change until you save.
2. Filling in the Trial Form as a Manager in MSS
When a manager opens the Manager Trial Form app in MSS, the Employee list shows their direct reports only. After choosing an employee, the screen opens with three tabs:
- Employee Data: name, personnel number, cost center, position, school, the start and end dates of the trial period and the Remaining Days, which tells the manager how much time is left to submit the form. Your company's information notes are shown below.
- Evaluation Form: answer the questions. Required questions and required comments cannot be left empty; when you click Submit Form with missing answers, the screen tells you how many questions are incomplete and takes you to them.
- History: which manager the evaluation is with, its status and status dates.
The submitted form is saved to the employee's infotype 0503. When the same employee is opened again, the last saved answers are loaded, together with who submitted the form and when. If the evaluation has been closed (for example HR completed the process), the form opens read-only.
HR uses the same screen under Trial Period > Trial Form. The only difference: HR is not limited to a team and searches the employee by personnel number or name, for example to fill in the form for a manager who has left.
Extending the Screen with a Scheme
The trial screen runs the scheme of its app at certain moments. With scheme rows, and without writing code, you can add behavior specific to your company:
| Moment | What the scheme gets | What the scheme can do |
|---|---|---|
| The page opens | The forms and the questions of the chosen form. | Change the questions, add information notes |
| An employee is chosen | The chosen employee and their last saved evaluation. | Fill the employee data (cost center, position, school, trial start/end date, remaining days) and the history; make the form read-only when it is closed |
| The form is changed | The new form chosen by the evaluator. | Show additional information for that form |
| The form is submitted | Runs after the form is saved to infotype 0503. | Forward the evaluation to HR or SAP, start a workflow |
The fields of the screen and every question can be hidden or shown by the scheme, using the question code. To skip a question for a certain position group, hide its code in the scheme.
3. Setting Up a JOB with a Scheme: Running Reminders Periodically
However well a form is designed, a form nobody fills in is of no use. Nobody needs to pull a list every morning to remind managers that "an employee's trial period is about to end". The JOB function of data schemes runs a scheme by itself at the times you set.
How Does JOB Work?
A few minutes past every hour, the system scans the JOB rows of the data schemes of all active companies and runs the schemes whose time has come and whose condition is met. Inside the scheme the JOB row does nothing else; it only answers the question "when should this scheme run". The schedule is written as JSON into Par1:
| Field | Description | Example |
|---|---|---|
| freq | Frequency: HOURLY, DAILY, WEEKLY or MONTHLY (required) | "DAILY" |
| hour | An hour or a list of hours (0-23, Istanbul time). When empty, HOURLY runs every hour, the others at 00:00. | 8 or [8, 17] |
| days | WEEKLY: 1 = Monday … 7 = Sunday. MONTHLY: 1-31 or "L" (last day of the month). Required for weekly and monthly. | [1, 3, 5] or ["L"] |
| begda / endda | Date range in which the job is valid (YYYYMMDD) | "20270101" |
| user / pernr / langu | User, personnel number and language of the run (JOB and TR by default) | "HRADMIN" |
| data | Values put into container.Data at the start of the run | {"days": 15} |
A few examples:
- Every day at 06:00:
{"freq": "DAILY", "hour": 6} - Weekdays at 08:00 and 17:00:
{"freq": "WEEKLY", "days": [1, 2, 3, 4, 5], "hour": [8, 17]} - On the 1st and 15th at 09:00:
{"freq": "MONTHLY", "days": [1, 15], "hour": 9} - On the last day of the month at 18:00:
{"freq": "MONTHLY", "days": ["L"], "hour": 18}
For rules a calendar cannot express, write a condition into Par4 of the JOB row. It is checked right before the run against the system date (SysDay, SysMonth, SysYear). For example, {"!=":[{"var":"SysMonth"},8]} pauses the job in August.
Example: A Trial Period Reminder Scheme
The data scheme below runs every weekday at 08:00 and sends the employees whose trial period ends in 15 days or less to your reminder service. The service can live in SAP or in your own system, and can e-mail the managers or create tasks for them.
| Seq | Function | Par1 | Par2 | Par4 (Condition) |
|---|---|---|---|---|
| 10 | COM | Remind about trial periods that are about to end | ||
| 20 | JOB | {"freq": "WEEKLY", "days": [1, 2, 3, 4, 5], "hour": 8, "data": {"days": 15}} | ||
| 30 | API | {"link": "https://…/trial-reminder", "method": "POST"} | container.Data | {"==":[{"var":"PageEvent"},"Job"]} |
The condition on row 30 makes sure the API call is made only when the JOB runs the scheme: in a job run PageEvent is Job. If the same scheme is also called from a screen, the reminder is not sent twice.
Good to Know
- Hourly resolution: jobs run on the hour; there are no minutes. All times are Istanbul time.
- At most once an hour: even if several JOB rows of a scheme fall into the same hour, the scheme runs only once in that hour.
- Days a month does not have: a day like
31runs on the last day of 30-day months. - User and authorization: by default the scheme runs as user
JOBwithout roles. If some steps need a certain user or personnel number, useuserandpernr. - Stopping: deactivating the JOB row (Deact) stops the job; clearing the executable flag of the scheme stops the scheme entirely.
- Errors: an invalid schedule, an invalid condition or a scheme error is written to the system error log. Turn on detailed logging of the scheme to follow each row.
Best Practices
- Keep the form short. A form a manager can fill in five minutes is a form that gets filled in. Focus on questions that actually drive your decision.
- Require comments on critical questions. A manager who answers Yes to "Is there anything that prevents the continuation of the contract?" should explain why; HR needs it for the next steps.
- Choose meaningful question codes. You will use them in reports and schemes.
- Start reminders early enough. In a two-month trial period, reminders from 15 days before the end leave the manager time for a conversation.
- Try a JOB in a short date range first. Limit the job to a few days with
begdaandendda, check the results, then remove the range.
Ready to Explore OrchestraHCM?
To see the trial period evaluation and scheme automation in your own organization, get in touch with us.