Application Drop Management

The Application Deletion is a built-in flexible flow to ensure the "Dropped" Application records are deleted from the system. When the imported Application record status is "Missed" or when the Drop Application attribute is manually marked as “True” for an Application by the Content Specialist, the Application Deletion flow is initiated. Once the application is marked as dropped, the system ensures that the user will not be able to search the respective Application record.

Scenario

Consider that Application "FPPX Shock Absorber" with "Record Status" is Missed, the Application Deletion flow is initiated to ensure the application is deleted from the system.

The following lists the sequence of steps for the Application in this use case:
app-delete-wf-image(1)

You have imported the Application "FPPX Shock Absorber" via ACES XML file and the "Record Status" is missed, then the Application Deletion flow is initiated.
If Content Analyst wishes to delete the Application, then the Approver must manually click Delete. The Application record is deleted and the application record is exported in RSJSON format and the record cannot be viewed in the search result.

Multi-load Application Drop Management

The dropped applications will be ignored for processing in any of the subsequent loads until the Application is reloaded as New.

The App behaviour for various drop scenarios up to five loads is described:

Load Number	Load Scenario	Status
Catalog loaded for the first time	The vehicle coverage happens for the first time.	The Net Change Status of Application Group and Application will be New Coverage.
Load 2	Some Applications are missing from the XML.	The missing Applications will be marked as Dropped. The remaining Applications will be marked as No Change. The Net Change Status for Application groups will be marked as Change.
Load 3	Some Applications from the remaining Applications are dropped and some Applications are added new.	The missing Application will be marked as Dropped. The new Applications will be marked as New. The remaining Applications will be marked as No Change. The Net Change Status for Application groups will be marked as Change.
Load 4	All the Applications in the Application group will be dropped.	All the Applications will be marked as Dropped. The Application group will be marked as Dropped Coverage.
Load 5	All the previously dropped Applications come back for the processing.	All the Applications will be marked as New. The Net Change Status for application groups will be marked as Change.

Notes:

If an Application was dropped in a previous load, Autoapp ignores it in subsequent loads, and only Applications dropped in the current load are processed.
If all applications within an application group in the current load are marked as Dropped, then the net change status of the application group is set to Dropped Coverage.

Scenario

Consider a scenario where PEAK Engine Coolant / Antifreeze (Catalog) is our entity and the following three loads are processed:

Load 1: In the first load, 24 new Applications were added.
Load 2: During the second load, 12 Applications were dropped, out of which 6 Applications were dropped due to Note Change. For Applications that are dropped due to Note Change, new Applications are created. Hence, 6 new Applications were created. So, in the second load 18 Applications were present.
Load 3: In the third load, no new applications were added. So, in the third load 18 applications will be present.

To review the above loads in a catalog by its load history:

On the navigation menu, click Search > Search Applications app.

Result: The Search Automotive Domain page is displayed.
Click the required Catalog Name link.

search_auto_domain

**Result:** The **Catalog Manage** page is displayed.

Click the Load Lineage tab.

home_load_lineage

**Result:** The **Load Lineage** grid displays the load details in a tabular format. A sample screenshot is displayed.

load_lineage_loads

You can click the Task ID link to view the details of the respective loads by navigating to File Submission Report tab.

The following screenshot displays the Load 1 details:

The following screenshot displays the Load 2 details:

The following screenshot displays the Load 3 details:

Application Drop Management due to Note Change

Autoapp drops the Applications if there any changes to the Application note. When an existing Application in the system is reloaded with changes made only to the Note section, keeping rest of the information same, AutoApp drops the original application and creates a new one. The original Application is marked as "Dropped," while the new one is treated as “New”.

Scenario

Consider you have the following loads:

Load 1: In this load, Application with the Note, LS Swap and RS Swap, are added.
Load 2: In this load, all the Application data mentioned in Load 1 remains same except for the Note. A new Note, Hemi Swap, is added to the Application.

Load 1

The following is a sample XML Snippet for Load 1:

<App action="A" id="1">
  <BaseVehicle id="18810"/>
  <SubModel id="2666"/>
  <Region id="3"/>
  <Note>LS Swap</Note>
  <Note>RS Swap</Note>
  <Qty>1</Qty>
  <PartType id="12907"/>
  <Position id="22"/>
  <Part>VEN_1203</Part>
</App>

The following is a sample XML file for Load 1:

Sample Load 1.xml

The above load creates the Application with two notes, and the Net Change Status value is set to New Coverage. A sample screenshot of the created Application with Note in first load is displayed.

relations_notes

Load 2

The following is a sample XML Snippet for Load 2:

<App action="A" id="1">
  <BaseVehicle id="18810"/>
  <SubModel id="2666"/>
  <Region id="3"/>
  <Note>LS Swap</Note>
  <Note>RS Swap</Note>
  <Note>Hemi Swap</Note>
  <Qty>1</Qty>
  <PartType id="12907"/>
  <Position id="22"/>
  <Part>VEN_1203</Part>
</App>

The following is a sample XML file for Load 2:

Sample Load 2.xml

Upon uploading the xml in second load, the originally created Application is dropped, and a new Application is created with the Note. Sample screenshot of Application with Notes in the second load:

relatons_add_notes

Since, the existing Application is dropped due to a change in note only, the Vendor Documentation attribute value is updated as Notes change only.

notes_change_only

You can view the number of Applications that are dropped due to Note Change in the File Submission Report. A sample screenshot before the second load is displayed.

no_dropped_note_change

A sample screenshot of File Submission Report after the second load is displayed.

notechange_col

A sample screenshot of Load Lineage tab after the second load is displayed.

load_lineage_secondload

Note:

If all the Applications in an Application group are dropped due to Note Change, then Only Note Changed? attribute value is set to TRUE in the Application group.

only_note_changed

Walkthrough

Watch this walkthrough to navigate through the Application Drop Management flow.