This tutorial will show how to set up the request module in N-OC. The request module is very much customized, which mean that without Aviolinx Support you can only use the "Days Off" requests. Many parameters has to be set before the crew can request from the Mobile. Note: Crew does not have access to Requests from the Cloud entry point.
| Period Rules: Name: | Mandatory | Period Type: | Request | Data Type | HumanResource | Filter: | Apply a filter. The filter will be the link to the Request Group filter. | Time Mode | Select the time mode you want to use for the requests. | Type: | Monthly, Rolling, Half monthly. Select the length that will be used by the Request group rule. | | | | | Period: Name: | Mandatory | Shortcode: | Optional | Type: | Request | Rules: | Period rule | Start/End | Mandatory. | Data Input start/end | Mandatory. This period is when it is possible for the crew to add requests, the period will normally be before the Start/End period | | | | | Contracts: You must create "Contracts" for each crew type. And to make "Request" available to a crew member, a contract must be linked to the crew. Name: | Mandatory. | Company: | | Email types: | | Title | | Part time percentage: | Part time percentage, will be used by the Request Group Rule. | | | In the HR section on the crew, you must add a contract. | | | | Request Group: For each filter you can make a sub-group that will apply to the contract percentage. Name: | Mandatory. | Filter: | Mandatory. Apply to the periods and contracts. | Max shift requests: | nbr of request for reference activities. | Max qual/rank coverage: | percentage of coverage of the total number of crew in the filter group. | Percent from/To: | percent. will apply to the contract percentage. | Max days off: | number | Max days off in a row: | | Day off reduction per vacation week: | | Max times off | | Times off reduction per vacation week: | | Days of requestable before/after vacations: | | Vac within period: | | Vac overlapping with period: | | Note: All fields must be filled, min. requirement is 0 (zero). Note: You have to save the sub-group before you can save the dialog. | | | | Request type: This is a place holder for request. | | | | Setup: | | AllowedRequestTypes: | | requestdayoffactivity: Select the Reference activity that shall be used for days off request. | | RequestSetup: | | Requesttimeoffactivity: Select the Reference activity that shall be used for time off request. | | RequestImportedNoteType Select the note type that is to be used on the roster. Normally it should be "Roster type" | | | | Mobile: Select the Request icon | | Click on the day where you want to place a request. | | | | Request type: Depending on the AllowedRequestTypes you will see the available request types. Priority: Will be used during the award if many crew have the same request. | | Day Off: | | Company Activity: Currently this option is not active | | Time Off: You can select if there should be shifts a defined time before or after the time off. | | Shifts: Select a Reference Activity from the list. Currently you need help from AVX Support to enter the available activities into the database. | | | | | | See the Request: Currently you can only monitor the submitted request in Earth. The light blue is unhandled. The green has been awarded. The light green has been preliminary awarded. | | | | Award the request: At the moment you can only award the requests from Cloud. Select the Auto roster button | | When the Auto rostering window opens it is important that you select Save on submit. | | Enter the period and the crew you want to award, the human resource must correspond to the filter you have in the request group. | | Create a template for the request. Type: | Requests | Request Types: | DayOff | Request Group: | The Request group | Actual run | Unticked: The award is preliminary, and the result can't be saved. Ticked: It will be the final run, and the result will be saved to the crew. | | | | | | | The result will be shown in the events window. Select Submit and the result will be saved to the database. | | Awarded requests: The awarded requests are shown in dark green. | | Preliminary awarded: The preliminary awarded requests are shown in light green. The crew can delete the preliminary awarded request. | | |