We made a few changes to the page where you Generate your Road Permits. There is nothing new to the process, we just made some changes to make it clearer on how data will be outut to your XML file.
- Road Permit Application Purpose - When generating the XML file, Phoenix Connect will ALWAYS write out an Application Purpose = 'A' (Amend) at the Road Permit level.
Section ID - you can now click on the Section ID to bring up the Edit Page
Example: Section 1900 in image below, you can use it to enter in the missing Amendment Type
- Purpose - we added this column so you can set the Application Purpose for each Section.
We are no longer looking at the RRS Generated date to determine what Application Purpose will be written out to the XML File. Phoenix will now look at the new Purpose column on the Section(s).
- When you first enter the Page, on Section(s)
- Purpose will default to 'N-NEW', if there is No RRS Generated Date
- Purpose will default to 'A-AMEND', if an RRS Generated Date exists
- If it applies, you can select the Purpose based on based on the Section(s) scenarios
- See Screen Shot Example Below: We generated a file to amend RP R12345 to Section 1900 and 259 and add Section 82A. When the file is generated, the RRS Generated date will be filled in. When the file was uploaded to ESF, there was a business rule failure. You fix the issues and then come to the Generation page again. Although the Purpose will default to 'A-Amend' for Section 82A (because FTA Generated is filled in), you can select 'N-New' so that the correct Applicaiton Purpose is written out to the XML
- You can select the Purpose based on each Section(s) scenario
- N-New will set the Application Purpose to 'N' - a New Section being added to the Road Permit
- A-Amend will set the Application Purpose to 'A' - Amending a Section that already exists on the Road Permit.