Set this field to True if you want to submit page in Ajax mode. In Ajax mode, page will be submitted asynchronously and user will not notice a page flicker.
When the field has a Description, the text here displays in that description. Blank and spaces are accepted values for this property.
Whether a not a field has a description is determined by the section the field is in. Each section has a property called “Field Description” which has options to either not display a description (Field Description: No) or where it should be displayed in relation to the field (Field Description: left, right, top).
|Enabled, RenderIfNotVisible, ShowIfLoggedIn, Visible|
User of OnLoad and OnPreRender process is no longer recommended. You should use process data source.
InvokeOnLoad : Use this to invoke webpart OnLoad process before a webpart load.
InvokeOnPreRender : Use this to invoke webpart OnPreRender process before a webpart load.
Active is defaulted to true. When true the field gets added to the page and can be used. If false the field is not added to the page and its value can not be used. It is as good as deleted. Use this if you are not sure to delete the field.
|CellPadding, CellSpacing, Height, Width|
Use NoOfColumns to lay out sections in webpart.
Following picture demonstrate a webpart with four sections. Number in box repersent NoOfColumns. NoOfColumns = 0 means all section will be laid out in one row no matter how many.
|DisplayProgressAnimation, ProgressAnimationImage, ProgressAnimationText|
Use these properties to show progress animation when you submit a form. This can be used for both ajax and non-ajax mode.
These properties are available for both webpart and field level. Field level properties will override webpart level.
DisplayProgressAnimation must be True for this to work.
If Progress animation url is left blank, it will use images/EP_Progress.gif by default.
These two properties are used for adaptive design for phone display.
RWDAutoFormat : By default EASYProcess will does auto format for a control for adaptive design. For example, section NoOfColumns will always be set to 1 for phone display. By making RWDAutoFormat to false, you can stop such format from happening automatically. This property is only available at WebPart and Section level.
RWDVisibility : Its value can be All, Desktop, Phone. ‘All’ means this control will display in both desktop browser and phone. Desktop will force this control to display in desktop browser, Phone will force this control to display in phone browser. If value is blank, then it will default to ‘All’.
SecurityLevel should be used to secure a webpart for logged in users. By default, if a webpart inherits a security level from page. But if a webpart is being displayed in webpart only page such as webpart window, webpart tester, you can secure this webpart using security level. A value more than 0 means it can only be seen by a user with security level equal or higher. To understand how authorization works in EASYProcess, click here.
|HeaderTableClass, HeaderTableStyle, MainTableClass, MainTableStyle, SectionCellClass, SectionCellStyle, SectionRowClass, SectionRowStyle, SectionTableClass, SectionTableStyle, SkinId|
A webpart has three areas that can be styled, MainTable, HeaderTable and SectionTable, see picture below. These Class and Style properties are associated with these areas. There are three ways you can specify values for these properties.
- Use SkinId. A skin is a predefined collection of classes for a particular control. Once a SkinId is specified for a control, a set of classes in that control will be automatically set. For example, MainTableClass will be ‘WebPart-<SkinId>-MainTable’ or ‘Section-<SkinId>-MainTable’. Every control defaults to SkinId = ‘Default’. You can have multiple skins for a particular control but only one can be applied at a time. Values for these classes are specified using EASYProcess CSS feature. To understand how CSS and Skin Id works review document here.
- Use your own class names. It will override skin based class name if SkinId is specified. You should use this feature if for a particular webpart/section/control, you like most of the skin classes but you want your own header class. Make sure you define those class names using EASYProcess CSS feature or in your own CSS.
- Use inline styling using MainTableStyle, HeaderTableStyle etc. Any value specified in these styles will be applied directly. You can use EASYProcess style builder to create style string.
- To style other elements in webpart, which are children of these areas, use CSS selectors for children.
To understand where these styles and classes apply, see picture below.
|DeploymentId, Filter10Name, Filter10Value, Filter1Name, Filter1Value, Filter2Name, Filter2Value, Filter3Name, Filter3Value, Filter4Name, Filter4Value, Filter5Name, Filter5Value, Filter6Name, Filter6Value, Filter7Name, Filter7Value, Filter8Name, Filter8Value, Filter9Name, Filter9Value, WebPartId|