AD0-E902 Dumps With Exact Questions and Answers

Understanding the Date Transformation:

Input:March 3, 2021, 10:34 AM

Output:March 1, 2021, 10:34 AM

The transformation subtracts2 daysfrom the input date without altering the time.

Why Option A is Correct:

subDays(now,2) subtracts exactly 2 days from the given date and time.

It preserves the time component of the input (10:34 AM) while shifting the date backward by 2 days, which matches the given output.

Why the Other Options are Incorrect:

Option B ("addHours(now; -48)"): While subtracting 48 hours also results in a 2-day difference, this approach directly modifies the time. The resulting time could shift if the operation crosses daylight saving changes or edge cases with leap seconds. It is less reliable compared to subDays.

Option C ("addDays(today; -4)"): This would subtract 4 days, which does not match the transformation shown in the example.

References and Supporting Documentation:

Adobe Workfront Fusion: Date and Time Functions

Workfront Community: Using Date and Time Expressions

Step by Step Comprehensive Detailed Explanation:

Understanding the Problem:

The scenario is triggered by a project status update.

After the scenario runs, it updates the project status again, which re-triggers the scenario, creating aloop.

The goal is to prevent the scenario from re-triggering itself.

Option Analysis:

A. When using instant triggers, finish the scenario with the Break directive to prevent the record from being updated again:

Incorrect. The Break directive is not used to prevent updates; it is used to stop further iterations of a scenario. It does not address the root cause of the loop, which is the re-triggering by updated records.

B. Create a filter after the instant trigger that only passes records that have not been updated by Fusion:

Correct. Adding a filter ensures that only records not recently updated by Fusion are processed. This prevents Fusion from re-triggering itself on the same record.

For example, you could use a condition to check if the Last Updated By field does not equal the Fusion user or if the Last Update Date is older than a certain threshold.

C. Schedule the instant trigger to only run at intervals to prevent Fusion from thinking the record has been updated after each run:

Incorrect. Instant triggers are event-driven, and their purpose is to respond to changes immediately. Scheduling them would negate the benefit of instant triggers and does not solve the root problem.

Why Filtering Records is Best:

Targeted Control: A filter after the trigger ensures only relevant updates (e.g., those not caused by Fusion) are processed.

Prevents Loops: By excluding records updated by Fusion, the scenario avoids re-triggering itself.

Maintains Performance: Filtering prevents unnecessary processing of irrelevant records, improving efficiency.

How to Implement:

After the instant trigger module, add a filter module.

Configure the filter to check the Last Updated By field or a custom flag indicating if the update was performed by Fusion.

Example: Last Updated By ≠ Fusion User or Update Flag ≠ True.

If a custom flag is used, ensure the flag is set when Fusion updates the record.

Alternative Solutions:

Add a custom field (e.g., "Updated by Fusion") that Fusion sets when it updates a record. This can also be used in the filter condition.

References:This approach aligns with Fusion best practices for preventing infinite loops caused by scenarios re-triggering themselves. Filtering ensures the scenario runs only when necessary, avoiding redundant processing and maintaining performance.

Understanding the Requirement:

The project name in Workfront must include:

Purchase Order Number (PO#).

Name of the product.

PO Fulfillment Date (formatted as YY/MM/DD).

If a discount is provided, append the discount percentage and the approver's last name in the format: 15% Discount - UserLast.

Example Output:

sql

Copy

2837 - Compendium-Premium Running Shoes - 21/02/16 - 15% Discount - UserLast

Why Option A is Correct:

The expression in Option A achieves the desired result step-by-step:

3.PO#: Includes the PO number.

3.Name: Appends the name of the product.

formatDate(3.PO Fulfillment Date, YY/MM/DD): Formats the PO Fulfillment Date in the desired YY/MM/DD format.

if(3.Discount Provided? = "Yes"; "- " + 3.Discount % + " Discount - " + 3.Approver Last Name):

Uses the if function to check if a discount was provided.

If "Yes," it appends the discount percentage (3.Discount %) and approver's last name (3.Approver Last Name) with the required format.

Why the Other Options are Incorrect:

Option B:

The expression is incorrect because it places if(3.Discount Provided?...) directly after PO Fulfillment Date without using formatDate for date formatting. This results in an unformatted date.

Option C:

Uses parseDate instead of formatDate, which is incorrect in this context. parseDate is used to interpret strings as dates, not to format dates for output.

Option D:

The expression does not include any conditional logic for checking if a discount is provided. It simply appends Discount - Approver Last Name regardless of whether a discount was given.

Steps to Use the Expression in Workfront Fusion:

Place the expression in the module that defines the project title in Workfront.

Map the fields (PO#, Name, PO Fulfillment Date, etc.) to the respective columns from the CSV data.

Test the scenario to ensure the output matches the desired format.

Final Expression (Option A):

3.PO# + " - " + 3.Name + " - " + formatDate(3.PO Fulfillment Date; YY/MM/DD) + if(3.Discount Provided? = "Yes"; " - " + 3.Discount % + " Discount - " + 3.Approver Last Name)

References and Supporting Documentation:

Adobe Workfront Fusion Functions Documentation

Workfront Community: Handling Conditional Logic and Date Formatting