In a Fusion scenario, a new project in Workfront will trigger the creation of a new project in ServiceNow. The name of the project in ServiceNow will be constructed in the following format: Two Digit Year - Reference Number - Project Name Which expression will generate the correct string?
Correct Answer: C
* Understanding the Requirement: * The desired output format for the project name in ServiceNow is:Two-Digit Year - Reference Number - Project Name * This requires dynamically constructing a string by combining: * The current year in a two-digit format. * ThereferenceNumber(a variable or input). * Thename(a variable or input, likely the project name). * Why Option C is Correct: * The concat function combines multiple strings into a single string. * Expression: concat(formatDate(now;YY), " - ", referenceNumber, " - ", name) * This ensures proper formatting with hyphens and spaces between the elements. * Breaking Down the Components: * formatDate(now;YY): Retrieves the current year in a two-digit format (e.g., "23" for 2023). * " - ": Adds the required separator. * referenceNumber: Dynamically adds the reference number. * name: Dynamically adds the project name. * Why the Other Options are Incorrect: * Option A ("formatDate(now;YY) - referenceNumber - name"): * This is not valid because it does not explicitly use a string concatenation function. * Option B ("join(formatDate(now;YY) - referenceNumber - name"): * The join function is used for concatenating elements of an array, not individual strings. Since the inputs are not in an array, this function will not work. * How This Solves the Problem: * The concat function correctly constructs the string with the desired format, dynamically generating the project name for ServiceNow based on the given inputs. References and Supporting Documentation: * Adobe Workfront Fusion Functions Documentation * Workfront Community: Using the concat Function
Question 7
A Fusion user notices that a third-party web service is sometimes returning a connection error -" "service is not reachable". However, the module executes successfully a few minutes later in a new execution. Which action increases the success rate of the executions?
Correct Answer: B
When dealing with intermittent errors, such as "service is not reachable," the default error handling in Adobe Workfront Fusion is often sufficient to improve execution success rates. * Default Error Handling: * Fusion automatically retries operations when transient errors, such as network or connection issues, occur. * By leveraging this built-in functionality, the system will attempt to re-execute the failing module after a brief delay, which is often enough for the external service to become reachable again. * Why Not Other Options? * A. Adding an error handler that will notify the system owner: While notifying the owner can be useful for monitoring purposes, it does not directly address improving the success rate of executions. * C. Adding a Break directive to the module: Adding a Break directive will stop the execution entirely, which is counterproductive in this case, as the service typically becomes reachable again after a short time. References: * Adobe Workfront Fusion Documentation: Default Error Handling Mechanisms * Experience League Community: Managing Intermittent API Errors in Fusion
Question 8
A customer wants all their Salesforce Opportunities to sync with their connected projects in Workfront - approximately 20,000+ projects. After the admin sets a Workfront Fusion scenario to run each night and perform this action, the scenario is run once to test. After 40 minutes, it unexpectedly stops running. Why did this occur?
Correct Answer: C
* Understanding the Issue: * The customer is syncing20,000+ Salesforce Opportunitieswith Workfront projects using a scheduled Fusion scenario. * After running for 40 minutes, the scenario unexpectedly stops. * Why Option C is Correct: * Workfront Fusion Execution Timeout: * Fusion scenarios have a default execution timeout of40 minutesper run. * If the scenario exceeds this time limit, Fusion automatically stops the execution to avoid resource overuse. * Handling Large Data Sets: * Scenarios involving large datasets (like syncing 20,000+ records) may require optimizations, such as breaking the data into smaller chunks using paginated requests or iterators. * In this case, the scenario stopped because the execution timeout was reached, not due to API limits or webhook restrictions. * Why the Other Options are Incorrect: * Option A ("Workfront API call limit"): * While Workfront does have API rate limits, they are generally generous and not the reason for the scenario stopping. Fusion scenarios are designed to manage API calls efficiently. * Option B ("Fusion times out if processing over 2000 records in 40 minutes"): * This is incorrect because Fusion does not have a hard limit on the number of records processed in 40 minutes. The timeout is time-based, not record-based. * Option D ("Workfront API stops webhooks after 2000 hits in 10 minutes"): * This does not apply to Fusion scenarios. Webhooks are separate from the API calls initiated by Fusion. * How to Resolve the Issue: * Split the Data: Use pagination or batch processing to divide the 20,000+ records into smaller chunks (e.g., 1,000 or 2,000 records per run). * Adjust Scheduling: Schedule the scenario to run more frequently with smaller batches, ensuring all records are synced over multiple runs. * Use Iterators: Add an Iterator module to loop through smaller subsets of data, preventing the scenario from exceeding the execution timeout. * Steps to Optimize the Scenario: * Add aSearch Moduleto retrieve opportunities in smaller batches (e.g., using limits or pagination parameters). * Use aRepeater Moduleto process each batch iteratively. * Save the scenario and schedule it to run nightly or more frequently, depending on the sync requirements. References and Supporting Documentation: * Adobe Workfront Fusion: Execution Timeout Limits * Workfront Community: Managing Large Data Sets in Fusion Scenarios By optimizing the scenario to handle smaller batches of data, the admin can avoid the execution timeout issue and ensure successful syncing of Salesforce Opportunities with Workfront projects.
Question 9
A user queried Salesforce for user information, and it returned a name, email address, and user ID. The user would like to assign a task in Workfront. Which steps are required to assign the task?
Correct Answer: B
* Step 1: Query Workfront for User Based on Email Address * Salesforce provides the email address of the user. Since Workfront uses user IDs for task assignments, the email address can be used as a unique identifier to query Workfront's database. * A query module in Workfront Fusion retrieves the corresponding Workfront user ID using the provided email address. * Step 2: Assign Task Using Returned ID * After retrieving the Workfront user ID, use it in the assignment field of the task module in Fusion. * The task assignment process requires a valid user ID, ensuring proper linkage and assignment within Workfront. * Why Not Other Options? * A. Assign the task using the provided user ID > add the user ID to the assignment field: The Salesforce user ID is not recognized by Workfront. It is necessary to query Workfront to convert the email into a Workfront-compatible user ID. * C. Query Workfront based on the user's name > assign task using returned email address: Workfront uses user IDs, not email addresses, for task assignments. Names are also not unique and could cause assignment errors. References: * Adobe Workfront Fusion Documentation: Task Assignments Using User IDs * Experience League Community: Mapping Salesforce Data to Workfront Tasks
Question 10
A custom API call to a web service is used inside of a high volume iteration. The module that calls the web service sometimes returns an error - 429: Too many requests. Which two actions may be used to address this error? (Choose two.)
Correct Answer: A,C
When encountering the error429: Too many requests, which indicates the web service is being overwhelmed by requests, the following actions can help: * A. Add a Sleep Module: * Adding aSleepmodule introduces a delay between iterations, reducing the frequency of API calls. * By slowing down the rate of requests, you avoid hitting the rate limits of the web service, thus reducing the chances of receiving a 429 error. * This approach is useful for managing high-volume iterations without overloading the external service. * C. Add a Module to Test the Service for Errors: * Adding a module to test the service's response before making a call can help prevent the 429 error by checking if the service is ready to handle requests. * This preemptive check allows the scenario to conditionally execute, ensuring that it doesn't overwhelm the service and respects the API rate limits. * Why Not Other Options? * B. Use an Ignore Directive: Ignoring errors can be risky because it would cause the scenario to ignore 429 errors, possibly leading to failed API calls that are not addressed. Ignoring an error doesn't solve the issue of too many requests being sent to the service. * D. Use a Break Directive: TheBreakdirective would stop the execution, which is counterproductive when trying to resolve the issue by reducing the rate of requests. It would not address the root cause of too many requests. References: * Adobe Workfront Fusion Documentation: Handling API Rate Limiting with Sleep and Error Handling * Experience League Community: Managing Web Service Errors in High-Volume Iterations
