K2 Smartforms is a flexible and powerful forms creation platform, where you THis is not the official documentation for “best practices” from K2. Although some of the planned features in (comments at last!) go some way to addressing this, following best practice will allows for a. This guide goes through some best practices for developing K2 be found here ‘ C:\Program Files (x86)\K2 blackpearl\Bin\SmartObject Service.
|Published (Last):||2 August 2015|
|PDF File Size:||4.20 Mb|
|ePub File Size:||19.21 Mb|
|Price:||Free* [*Free Regsitration Required]|
The form description needs to be filled in with a basic description of what it does and also its story blackpdarl and form number. This will make it easier for people to easily identify what the form does what it relates too. The name backpearl the view is made up in the same way as a Smartform. The only difference is that instead of. The view description needs to be filled in with a basic description of what it does and also its story number.
This will make it easier for people to easily identify what the view does what it relates too. The size is only a guide and common sense must still be used for controls apart from the label control.
Using drop down lists to select reference data and for most cases is an acceptable approach as everybody knows now to use a drop down list. But it does have a couple of drawbacks. So we do have an answer to this and that is to use to the picker control instead.
This will allow for speedier loading times and also allows the user to search for the specific data in an easier fashion. The rules for moving to a picker control is if the reference data is longer than 20 rows then use a picker control. You still setup the control in exactly the same way as you would a drop down list.
The only differences you can choose which properties can be searched against. To do this do the following steps.
Please make sure that data caching is blackpearo enabled on your data list controls like dropdown lists etc…. The pattern for RCT is that we have smart views and dummy forms.
So to get this to work properly we have use unbound rules. Due to the amount of rules being called on an editable list, blackpeal is new approach that dramatically reduces those calls. Add in any other additional parameters you will require such the rest of the best practice parameters.
Best Practice for developing K2 Apps
Create an unbound rule to either save or update the data depending on if the parameter id is populated like in step 9. Now that we have built the rules to save and update and load the information we can now add it to the list view.
Create a rule that when you click on the list item it transfers the primary key from the list into the view parameter. The edit rule should look like this. Work flow description should be filled in, so people know what it does and what story it relates to.
Data fields should be kept to a minimum and be used to only hold reference data like a primary or foreign key. Workflow activities should contain a name in what they do and the activity description should contain information such as whether there is a start rule or any escalations. Please note bestt is not ideal to put code directly into the workflow and you must consult with your K2 lead before doing so.
Lines Rules must have a label that is prefixed with Prcatices and then what the rule is checking for. As seen in the image above. The outcome lines should also be coloured to represent what they are doing and to also help visually navigate what the bset is doing.
Best Practice for developing K2 Apps – GreenEggs on K2
This is especially helpful in larger workflows. This sections looks at what is needed in each SmartObject. If you have a number of stored procedures that interact with same table, then same SmartObject can be used with the additional methods and properties added.
The name of the SmartObject like the rest of the K2 artefacts should przctices the same naming convention. The correct property type should be used and most prctices the time K2 will take care of this automatically.
The only exception is for file types. In some cases the correct method type is not selected. After the service object method is collected. So you once the service object method has been selected and the properties created and bound to the service object. You need to edit kk2 method and choose the correct method type.
An example of this sometimes a store procedure that returns a single row of data is sometimes returned as a list method. This is incorrect and would cause problems later on in the view practiices. Using this application allows you then to test your SmartObject to see if it is working correctly. From here we can now test the methods of the SmartObject.
She picked up lots of things, most notably how it is like to possess an incredible teaching style to let folks very easily have an understanding of several tricky topics. You actually exceeded our desires. I appreciate you for delivering the insightful, trusted, informative and fun guidance on that topic to Sandra.
I was studying some of your posts on this site and I conceive this site is very instructive! I have learn several good stuff here. Certainly worth bookmarking for revisiting.
I wonder how so much effort you place to create this kind of fantastic informative website. You are commenting using your WordPress. You are commenting using your Twitter account. You are commenting using your Facebook account. Notify me of new comments via email. When to use a drop down list or a picker control. Reducing the load with editable list views.
Any chance to fix it? Should be there now Like Like. I conceive you have observed some very interesting detailsthankyou for the post. I gotta favorite this internet site it seems extremely helpful very helpful Like Like.
Leave a Reply Cancel reply Enter your comment here Fill in your details below or click an icon to log in: Email required Address never made public.