Create a Form-Based Application With a SharePoint List

Examples

• Form Based Applications – SharePoint Data Source
• Examples - Step-by-step use case examples, information about what types of examples are provided in the AgilePoint NX Product Documentation, and other resources where you can find more examples.

Prerequisites

• AgilePoint NX OnDemand (public cloud), or AgilePoint NX PrivateCloud or AgilePoint NX OnPremises v7.0 Software Update 1 or higher.

Good to Know

• The application that uses SharePoint as a data source can only be accessed through the SharePoint Dashboard app or a SharePoint list. When you create a new list item, SharePoint uses the form-based application, instead of the default SharePoint list form.
• By default, the Person or Group column from a SharePoint list is mapped to a People Picker form control, and you can select individual users only. If you want to select both users and groups, you must either change the form control type or create a lookup for the People Picker form control.
• A New form for SharePoint form-based application does not support attachments. You can add attachments with an Edit form after a list item is created. This is a limitation for new list items in SharePoint.
• A forms-based application that uses a SharePoint data source supports SharePoint lists only. It does not support document libraries. For a SharePoint document library, create a form-based application that uses a different data source, such as Data Entities, and upload documents with metadata to the document library.
• The Standard List Form activity and Start List Form activity can not be used on the lists where forms-based application is created. The List Form activities are only for legacy applications.
• Data binding from eForm controls to a SharePoint list occurs only if a process starts from an application that uses SharePoint as its primary data source. If an eForm is part of a process that starts from SharePoint, it can not use data binding.
• SharePoint does not have a date-only data type. If you configure a field in SharePoint to show the date only, it is stored in SharePoint as date-time in UTC format. The regional settings of the SharePoint site where this value is stored can result in data changes based on the time zone.

  If you want to use time zone conversion for a date-only value in SharePoint, AgilePoint recommends you use a field that is not data-bound. If a SharePoint date-time field is configured to show the date only, a data-bound field will always send an absolute date.

• These time zones are not supported for SharePoint data-bound date-only fields. If the regional settings for your SharePoint site is configured to use one of these time zones, you might see a different date in the SharePoint UI.
  • UTC – 11:00 Coordinated Universal Time-11
  • UTC – 12:00 International Date Line West
• This procedure topic creates a new form-based application with these components:
  • A Create form where a runtime app user can enter data. This form is the main UI for the application.
  • An Update form where specific users can change the data that was entered on a Create form.
  • A View form that shows a list view of the data from all instances the Create and Update forms for your application.
  • A View form that shows a list view of the data from all instances the Create form that have been recently submitted for your application.
  • A View form that shows a list view of the data from all instances the Update form that have been recently submitted for your application.
• The form name is based on your SharePoint list name.

  Format:

  • New [List Name]
  • Update [List Name]
  • All [List Name, Plural]
  • Recently Created [List Name, Plural]
  • Recently Modified [List Name, Plural]

  Example:

  • New Customer
  • Update Customer
  • All Customers
  • Recently Created Customers
  • Recently Modified Customers
• By default, the runtime app user can change the form, but you can set the application permissions to configure which AgilePoint NX users can create or update form data.

  For more information, refer to How Do I Use Application Level Permissions?

How to Start

1. Click Build Apps .

   
   
   

2. On the Application Explorer screen, click Add App.

   
   
   

Procedure

1. On the Application Type screen, select Form Based Application.

   
   
   

2. Click Next.
3. On the New Application screen, complete these fields:

   
   
   

   Field Name	Definition
   Application Name	Function: Specifies a name for your application. Accepted Values: One line of text that can have spaces. Default Value: None Example: Refer to: (Example) Create a Process-Based Application for an Absence Request (Example) Create and Run a Form-Based Application with AgilePoint NX Data Entities
   Language	Function: Specifies the language for your application. Accepted Values: A language from the list. Default Value: None Accepts Process Data Variables: No
   Application Description	Function: An optional description for your application. Accepted Values: More than one line of text. Default Value: None

4. Click Next.
5. On the Select Primary Data Source screen, select SharePoint .

   
   
   

6. Click Next.
7. On the SharePoint Configuration screen, click the Configuration tab.

   
   
   

8. On the Configuration tab, in the Data Source Name field, enter a custom name for your SharePoint repository.
9. In the SharePoint list, select your SharePoint access token.

   To create a new access token, click Add Token . For more information, refer to Access Token for SharePoint.

10. Complete these fields.

    Field Name	Definition
    Site URL	Function: Specifies the URL for your SharePoint site. Accepted Values: A valid SharePoint site URL. Default Value: None Accepts Process Data Variables: No Example: http://[machine name]:[port]/sites/[site name] Note: You must include the /sites in the Site URL for the site to be created successfully. Form Based Applications – SharePoint Data Source
    List Name	Function: Specifies the name of your SharePoint list. Accepted Values: The name of your SharePoint list. Default Value: None Accepts Process Data Variables: No Example: Refer to: Form Based Applications – SharePoint Data Source

11. Click the Fields tab.

    
    
    

12. On the Fields tab, select the fields you want your form to contain.
13. Click the Related Entity tab.
    Note: The word entity on this screen refers to a container within your data model. For Data Entities or Salesforce, this container is called an entity. For a database, entity refers to a database table. For SharePoint Integration, entity refers to a SharePoint list..

    
    
    

14. On the Related Entity tab, select the child SharePoint lists to use in your form.
15. Click Finish.
16. On the eForm Builder screen, in the Toolbox, open any tab.
17. Drag a form control onto your eForm.
18. On the eForm Builder screen, configure your form as necessary.

    For more information, refer to eForm Builder.

    
    
    

19. Publish a form-based application.
20. Associate an AgilePoint eForm with a SharePoint List.
    • For SharePoint for Office 365, refer to Associate an AgilePoint eForm with a SharePoint List (Office 365).
    • For SharePoint in an on-premises environment, refer to Associate an AgilePoint eForm with a SharePoint List (On-Premises).
    .