Shared fields

From RPM Wiki

Table of contents
1 Summary
2 Details

2.1 Setup
2.2 More rules
2.3 Security
2.4 Fields

3 Future
4 History
[edit]

Summary

Allows fields to be added that contain information from something else in RPM like a customer, supplier, agency, or other thing that there are reference fields for.

[edit]

Details

[edit]

Setup

  • First page (add): user selects a parent reference field and a target shared field
    • Both are drop downs
    • Can't be changed after (edit skips this page)
    • If there are no eligible parent fields show an error message "An agency, rep, or customer reference is required" and just a "Cancel" button.
  • Second page (add/edit), typical field information with a few limitations and one addition:
    • Field (text box for field name)
    • Parent - disabled, can't edit (see above) but shows the name of the parent reference field
    • ---
    • Type - "Shared"
    • ---
    • Group: Drop down for field group membership
    • Repeating - Displays repeating value of parent (Shared fields are forced to same as parent reference field)
    • Shared - This is new and only shown for shared fields. This displays the name of the target field.
    • ---
    • Security - Shared fields are limited to "Hidden" and "Read".
  • Display in field list show the type as "Shared"
[edit]

More rules

  • If a parent reference field is deleted, all it's shared fields are deleted as well.
  • Shared fields can be added and removed from forms separately from the template just like any other field type.
  • Shared fields are not listed in views since views already have linked columns to provide this information.
  • Can not control a field group (but can belong to one like any field)
  • Can not be a status trigger
  • Can not be set by import
[edit]

Security

  • Security is determined by the form, not by the referenced object.
    • Example: If I build a template that allows agent users to "Read" a shared agency website field, then any agent user participant of the form will be able to see that field regardless of the selected agency in the parent agency reference field.
    • Example: I add a shared custom field that is hidden for agent users. In my form I make it "Read" for all users. Agent user participants of the form will now see that field's value.
  • Shared fields can not be "Edit" or "Required"
  • The default permissions for a new shared field is the permissions of the parent with the above rule meaning that "Edit" or "Required" become "Read".
[edit]

Fields

  • Agency reference
    • Primary contact (display as salutation first last)
    • Title
    • Email
    • Business phone
    • Home phone
    • Fax phone
    • Other phone
    • Website
    • Street address
    • City
    • State
    • Country
    • Zip code
    • Supplier exclusions
    • {each standard custom field}
    • Added
    • Modified
  • Rep reference
    • Primary contact (display as salutation first last)
    • Type (as of Shine)
    • Title
    • Email
    • Business phone
    • Home phone
    • Fax phone
    • Other phone
    • Company
    • {each standard custom field}
    • Added
    • Modified
  • Customer reference
    • Primary contact (display as salutation first last)
    • Title (use primary)
    • Email (use primary)
    • Business phone (use primary)
    • Home phone (use primary)
    • Fax phone (use primary)
    • Other phone (use primary)
    • Website
    • Street address
    • City
    • State
    • Country
    • Zip code
    • {each standard custom field}
    • Added
    • Modified
  • Account reference
    • Street address
    • City
    • State
    • Country
    • Zip code
    • {each standard custom field}
    • Added
    • Modified
  • Location reference
    • Street address
    • City
    • State
    • Country
    • Zip code
    • {each standard custom field}
    • Added
    • Modified
  • Supplier reference
    • Primary contact (display as salutation first last)
    • Title
    • Email
    • Business phone
    • Home phone
    • Fax phone
    • Other phone
    • {each standard custom field}

Only standard custom fields may be selected

  • Formatting fields would be useless
  • Reference fields can't be used for custom fields
  • Address fields for Customer reference fields refer to the address of the primary location. Address fields for Customer Account reference fields refer to the address of the primary location for the customer of the account.
[edit]

Future

  • Edit shared field values
  • Import shared field values
[edit]

History

Retrieved from "http://www.rpmsoftware.com/wiki/index.php/Shared_fields"
  • This page was last modified 19:16, 3 Aug 2010.
  • This page has been accessed 5795 times.