B: The approval step that you're configuring might be required only if specific conditions are met.
C: A conditional decision is a point at which a workflow divides into two branches. The system determines which branch is used by evaluating the submitted document to determine whether it meets specific conditions.
Reference:
https://docs.microsoft.com/en-sg/dynamics365/fin-ops-core/fin-ops/organization-administration/configure- conditional-decision-workflow

Instead navigate to the user interface forms section for the SalesTable form and create an extension.
Note: In Dynamics 365 Finance and Operations, the new fields will need to be added via a table extension. Create the extensions on the SalesTable.
Reference:
https://stoneridgesoftware.com/how-to-extend-sales-order-update-functionality-to-custom-fields-in-d365-finance-and-operations/

Explanation

Reference:
https://docs.microsoft.com/en-us/azure/devops/repos/tfvc/branching-strategies-with-tfvc?view=azure-devops

Explanation:
Box 1: Yes
Class extension - Method wrapping and Chain of Command.
The functionality for class extension, or class augmentation, has been improved. You can now wrap logic around methods that are defined in the base class that you're augmenting. You can extend the logic of public and protected methods without having to use event handlers. When you wrap a method, you can also access public and protected methods, and variables of the base class. In this way, you can start transactions and easily manage state variables that are associated with your class.
Box 2: Yes
In the following example, the wrapper around doSomething and the required use of the next keyword create a Chain of Command (CoC) for the method. CoC is a design pattern where a request is handled by a series of receivers. The pattern supports loose coupling of the sender and the receivers
[ExtensionOf(classStr(BusinessLogic1))]
final class BusinessLogic1_Extension
{
str doSomething(int arg)
{
// Part 1
var s = next doSomething(arg + 4);
// Part 2
return s;
}
}
Box 3: Yes
Instance and static methods can be wrapped by extension classes. If a static method is the target that will be wrapped, the method in the extension must be qualified by using the static keyword.
Box 4: No
Wrapper methods must always call next.
Note: Wrapper methods in an extension class must always call next, so that the next method in the chain and, finally, the original implementation are always called. This restriction helps guarantee that every method in the chain contributes to the result.
In the current implementation of this restriction, the call to next must be in the first-level statements in the method body.
Here are some important rules:
* Calls to next can't be done conditionally inside an if statement.
* Calls to next can't be done in while, do-while, or for loop statements.
* A next statement can't be preceded by a return statement.
* Because logical expressions are optimized, calls to next can't occur in logical expressions. At runtime, the execution of the complete expression isn't guaranteed.
Reference:
https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/extensibility/method-wrapping-coc

Parameters: EntireTable
Transaction: NotInTTS
Master Data: Found
Region specific master data: FoundAndEmpty
Explanation:
https://community.dynamics.com/365/financeandoperations/b/performancetipsandtricks/posts/dynamics-365-for-finance-and-operations-table-caching-basic-rules#:~:text=Entire%20table%20cache%20size%20determines,365%20for%20Finance%20and%20Operations.&text=Each%20AOS%20server%20can%20have%20its%20own%20cache%20settings.