New: Difference between revisions

From Accelerator for SageCRM
No edit summary
No edit summary
Line 46: Line 46:
     CustomContent - Basic HTML but no client script will be included.  
     CustomContent - Basic HTML but no client script will be included.  
     CreateScript items - Caption, Required,DefaultValue,ReadOnly (case-sensitive)
     CreateScript items - Caption, Required,DefaultValue,ReadOnly (case-sensitive)
    Methods - Context is not the same as in CRM. So things like CRM.GetContextInfo will not work as if it was in CRM except for the user entity. We have created a method called "GetContextInfo" that will work based on the context that a screen is called from (EG company/person). "CRM.FindRecord" and "CRM.CreateQueryObj" will also work.


PLEASE NOTE:
PLEASE NOTE:


Fields like "oppo_description" that are key fields and are set based on the email. So for those fields "DefaultValue" will not work.
Fields like "oppo_description" that are key fields and are set based on the email. So for those fields "DefaultValue" will not work.

Revision as of 14:39, 4 November 2021

The NEW menu is available on all menu bars in the task pane.

Clicking on an item loads a modal with the fields on it. The context with which something is created is important as this will preset some fields.

Click Save to Save the record and then the UI will show the summary of this record.


Deduplication is available on the company

and person screens



Customising

A. The screen fields are controlled by metadata.

The screens are called "ENTITYOfficeIntNew".


B. To add in a primary custom Entity*

   created using the entity wizard

Open the "...custompages/sagecrmws/web.config"

Edit the line "NewEntities"

EG..here we add in "Project"

   <add key="NewEntities" value="Company,Person,Lead,Cases,Opportunity,Project" />

C. Screen Scripting

Supported

   CustomContent - Basic HTML but no client script will be included. 
   CreateScript items - Caption, Required,DefaultValue,ReadOnly (case-sensitive)
   Methods - Context is not the same as in CRM. So things like CRM.GetContextInfo will not work as if it was in CRM except for the user entity. We have created a method called "GetContextInfo" that will work based on the context that a screen is called from (EG company/person). "CRM.FindRecord" and "CRM.CreateQueryObj" will also work. 

PLEASE NOTE:

Fields like "oppo_description" that are key fields and are set based on the email. So for those fields "DefaultValue" will not work.