What are the differences between dForms and eForms?

The designs for dForms and eForms are very similar; the main differences are in how users access them and what happens to them after submission.

dForms:

• dForms reside in Ariba Strategic Sourcing and Contract Management Solutions.
• Users open a workspace, select a dForm, fill it out, and submit it.
• No approval is necessary for dForms.
• Access to dForms is controlled by folder permissions; an administrator can organize them into logical folders so that users can easily find the ones they need.
• dForm data is reportable, but not exportable.

eForms:

• eForms reside in the Create menu in Ariba Procurement Solutions.
• eForms are approvable documents at the same level as other approvables, such as requisitions and invoices.
• Users select an eForm in the Create menu, fill it out, and submit it.
• Your site routes the eForm to approvers according to your organization's approval rules. Permissions grant group access to each eForm design.
• You can export eForm data for use in external systems.
• Like other approvables, eForms have default fields for adding comments and attachments.
• eForm designs let you specify a greater number of parameters, such as the form ID prefix and whether form data can be exported.

The field types available for each type of form are slightly different.

Other aspects of form design, such as Ariba expressions, enumerations, line-item tables, and flex master data are the same for the two types of forms.

Core Procurement > eForms
Strategic Sourcing > Strategic Sourcing - dForms