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):||28 October 2013|
|PDF File Size:||2.87 Mb|
|ePub File Size:||17.66 Mb|
|Price:||Free* [*Free Regsitration Required]|
Using this application allows you then to test your SmartObject to see if it is working correctly. Workflow activities should contain a name in what they do and the activity description should contain information such pracctices whether there is a start rule or any escalations. Everything in this post, your design, your reusable objects, your naming conventions, etc should be properly documented and regularly updated. You are commenting using your Facebook account.
So you once the service object method has been selected and the properties created and bound to the service object. The pattern for RCT is that we have smart views and dummy forms.
K2 Smartforms: best practices – How2 K2
If in doubt, do contact your K2 customer success manager to ask about these matters. Strictness of performance load time One reality we have to face: Both parties the developer and stakeholders alike should acknowledge that a tighter timeline will have higher risk for poorer quality.
Please make sure that data caching is not enabled on your data list controls like dropdown lists etc…. If you have strict requirements to load complex forms in a span of 3 seconds for example, you may gest to rethink about your decision to use SmartForms.
If you have a number of stored procedures that interact with practice table, then same SmartObject can practifes used with the additional methods and properties added. The only exception is for file types.
The name of the SmartObject like the rest of the K2 artefacts should carry the same naming convention. Net will still be the safest bet.
Fill in your details below or click an icon to log in: If you have stable requirements, you l2 start to properly plan your data model and plan your reusable SmartObjects, UI flow, and reusable Views.
Follow Blog via Email Receive notifications of new posts by email. Email required Address never made public.
Best Practice for developing K2 Apps
Rule interacts only with controls on that single view. This gives your project a solid foundation. This becomes even more critical in projects with large numbers of artifacts and practice developers. Email required Address never made public. I will create another blog post dedicated to this topic soon! The only differences you can choose which properties can be searched against.
Otherwise, if you need to interact with blackpearll not found in the current view, you can use parameters. The outcome lines should also be coloured to represent what they are doing and to also help visually navigate what the workflow is doing. Define consistent UI styling These are some examples of guidelines for your dev team: And so some developers prefer to put all their rules into their forms. First and foremost, bestt a realistic timeline that allocates enough time for technical design — so that your blueprint is properly planned before you actually start building.
To add a description in the Activity event. Are there complex UI requirements that are not out-of-the-box in K2 Smartforms? I was studying some of your posts on this site and I conceive this site is very instructive!
pracices By continuing to use this website, you agree to their use. Create Environment Variables Environment variables could be useful in 2 ways: Some rules can be called later.