Quantcast
Channel: Enterprise Software Design Blog » CRM
Viewing all articles
Browse latest Browse all 4

Extensible Design – Data Model and User Interface

0
0

As discussed in my earlier post(Extensibility Design), an extensible design provides the ability to customize an enterprise application software to server business needs of different customers. Extensibility is critical to the application software vendor especially if the software is delivered through a SaaS or On-Demand model. The underlying application architecture should support a metadata based model, which will provide a framework to extend the out of the box application to suite different customers’ needs. The framework should provide a generalized mechanism to construct application components to build the software.

The generalized mechanism for extensibility will mainly provide following three features.

  • Data Model Extensibility: The end users should be able to manage attributes with in a business objects. They should be able to add a new attribute of any data type and define rules for it.
  • UI Extensibility: The end users should be able to add new attribute to the UI forms as a field and the data can be added/modified using these fields. The field can be either simple editable text, number (such as amount, percentage), lookup or even media object (such as image, video) etc.,
  • Security Privileges: The design should take in to account that can extend a business object and once extended who can view and manage these extended attribute.

Data Model Extensibility

Data model extensibility is achieved through flexible attributes. Flexible attributes are generic attributes that is associated with a logical business objects. Flexible attributes are of generic data type (such as Raw) and can hold data of any type. The data will be stored as raw bytes and will be converted to appropriate data type on the business layer before transaction processing. An example of flexible attribute for CRM Opportunity object is given below.

UI Extensibility

UI Extensibility refers to the ability to add a field on runtime to a page. A ‘customize’ link will bring up the extensibility editor which will allow the users to create a new field in the form. The editor will prompt the user to enter the label and type. The types can either text, number of lookup. If lookup is chosen, then the editor will prompt the user to enter the lookup items. The user can also choose other properties such as required field and validation rules (not shown in wireframe below).

Security Privileges

The visibility of extended attributes and fields will depend on the security privileges. The attributes in the data model will inherit the data security policy defined for the logical business object and the function security will depend on any of the following.

  • Organization Hierarchy: The field can be made visible to the any of the organization hierarchy defined such as sales org, marketing organization etc.,
  • Employee Hierarchy: The field can be made visible to the any of the employee hierarchy defined. The administrator will choose a sales VP and all employees reporting under sales VP will see the fields.
  • All Users: The field can be made visible to all the uses with in a enterprise.

It should be noted that in a SaaS model, the customization will be visible only to those who extends the product. Subscribers’ from other customers will not be able to see these changes.



Viewing all articles
Browse latest Browse all 4

Latest Images

Trending Articles





Latest Images