Get production calendar Version 1 (Net)
Action group: Dates' conversion
Description
The action returns from the Orchestrator all dates from the specified production calendar.
Action icon
Settings of parameters
| Property | Description | Type | Filling example | Mandatory field |
| Parameters |
| Calendar name | The production calendar name. Action returns non-working day collection | Robin.String |
| Yes |
| Results |
| Result | Non-working day collection | Robin.Collection |
|
|
- The action must send a request to RMS (via the Agent) to retrieve all dates from the production calendar whose name is specified in the input parameters of the action. The action should return all dates as a collection of dates.
- In the collection, the dates should be immediately sorted by increment ( from the beginning of January to the end of December).
- If the action specifies a calendar name that does not exist in the Orchestrator database, the action returns an error with the appropriate reason for it.
- If there is some problem on the server side of Orchestrator and the request fails, the action also returns an error.
- RMC has a Standard Calendar that the user does not add and cannot delete. It is used when the user does not use production calendars. Therefore, there should not be an option to upload such a calendar. If you specify the name "Standard Calendar" in an action, it should return an error that no such calendar was found.
- The action only works in the Enterprise version.
Example of use
Task
There is a file in .csv format.
This calendar has been added to RMC under the name "Test Calendar". It is necessary to get the calendar dates to the collection and by indexes.
Solution
Use the actions "Get production calendar", "Get value by index".
Implementation
- Move the "Get production calendar" action to the workspace and fill the "Calendar name" parameter with the value "Test calendar".
- Move the "Get value by index" action to the workspace and fill in its parameters. Use as many actions as the number of values you want to get.
- Use as many actions as the number of values you want to get.
- Start the robot using the "Start" button in the top panel.
Result
The program robot completed successfully.
Example of one of the received dates:
A collection with 8 dates (the result of the "Get production calendar" action:
