External users

From Resco's Wiki
Revision as of 11:07, 15 October 2019 by Jzambor (talk | contribs) (External (portal) users: pic width 600 px)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

When creating App projects in Woodford, you can set up which users get what customization. For example, the app for sales representatives contains custom information relevant for their work, and the app for technicians can include different information. Both of these groups are usually internal employees.

Woodford also allows to create a custom app for external users, either those belonging to a particular CRM entity, for example Partners, or completely anonymous access with no authentication, for example customers.

Anonymous external users

With anonymous external users, all users will access the same content in the app. For example, the app can serve as a marketing channel, offering universal information about your products and services.

  1. In your CRM, for example Microsoft Dynamics, set up a new common user. Define a security role for this user. Either create a new security role, or assign an existing role with permissions that match the access level you want to grant to app users.
  2. In Woodford, create a new app project:
    • Set Type to Anonymous External User.
    • Server Alias is an identifier of your project. It must be globally unique among all external/anonymous projects. External users must enter alias as URL in the synchronization window of Resco Mobile CRM app. If you cannot save a new external project, it usually means that the alias is already taken. It must contain letters only.
    • CRM External URL: Specify the URL of your CRM.
    • CRM User is the user (license) used to access the CRM. It is the common user you created in step 1.
    • Password is the password of the CRM user.
      • You can also hide the sync dialog in your app, so the users don't need to fill in the information and connect automatically.
  3. Customize the project in Woodford to further define what the external users can see and edit. And to make sure that the app will represent your company's visual identity.

External (portal) users

External portal users need to log in access the app. This allows them to access your CRM content tailored specifically for them.

  1. In your CRM, for example Microsoft Dynamics, set up a new common user. Define a security role for this user. Either create a new security role, or assign an existing role with permissions that match the access level you want to grant to app users.
  2. Select an entity (standard or custom) that has fields for storing the user name and password of external users.
  3. In Woodford, create a new app project:
    • Set Type to External (Portal) User.
    • Server Alias is an identifier of your project. It must be globally unique among all external/anonymous projects. External users must enter alias as URL in the synchronization window of Resco Mobile CRM app. If you cannot save a new external project, it usually means that the alias is already taken. It must contain letters only.
    • CRM External URL: Specify the URL of your CRM.
    • CRM User is the user (license) used to access the CRM. It is the common user you created in step 1.
    • Password is the password of the CRM user.
    • Authentication Entity is the entity where the fields with user name and password are stored.
    • Password Format: Specify how the password is stored. Select Plain if you want them readable. Select Hash if you don't need to see the passwords.
    • User Name Field is the field on the authentication entity where the user name is stored.
    • Password Field is the field on the authentication entity where the password is stored.
    • CustomerId Field is the field that points to the parent entity record, which serves for filtering the records that users see.
    • Customer Lookup Field is the specific field that contains the name of the parent record. This is a part of the authentication that needs to be filled in. Then you can limit the records users will see (by using sync and view filters).
    • Registration Method represents the way how new users can be registered (their records get created in the Authentication Entity):
      • None – You need to create the External user manually in CRM before users can synchronize the app.
      • Direct – You can create a new External user with a registration form, after selecting REGISTER USER on Mobile CRM’s Sync dialog, a record will be created directly on the CRM server.
      • Web Service – Same as the Direct method, but data from the registration form will be sent to the Web Service that you want to use for creating the record. Please contact us if you want more information about this option.
      • Email – Same as the Direct method, but data from the registration form will be sent via an Email.
  4. When you use a registration method different than None, additional parameters appear:
    • Registration Service Endpoint: For email and web service registration, specify the end point.
    • Registration Form: Click it to set up the registration form. You can place any field from the Authentication Entity there. Of course, the User Name and Password field should be there as well. Also, don't forget to the Customer Lookup Field that will set up the parent record. For example:
    Registration form.png Registration form shown.png
  5. Customize the project to define what these external users can see and edit.

See also

  • Introduction: part 1 and part 2 Blog
  • How to set up a mobile application for external users: link Blog
  • How to use Sync Filter for external users: link Blog
  • How to track changes by external users: link Blog