Nov 14, A whitepaper containing advice and instructions for choosing, designing, deploying and maintaining process-driven applications with K2. Nov 14, WHITEPAPER: K2 BLACKPEARL BEST PRACTICES. PAGE 3. INTRODUCTION. In this whitepaper you will find practical guidance on best. Apr 21, K2 Smartforms is a flexible and powerful forms creation platform, where you can create your UI, and configure THis is not the official documentation for “best practices” from K2. .. Generate PDF files in K2In "SmartForms".
|Language:||English, Spanish, Portuguese|
|Genre:||Children & Youth|
|Distribution:||Free* [*Registration needed]|
Jun 20, Learn how to make use K2's PDF conversion feature, and make sure that you generate a K2 Smartforms: best practicesIn "SmartForms". The K2 blackpearl Core training course is designed to give participants the fundamental knowledge required . K2 workflows according to best practices and for. Adlib Enterprise for K2 blackpearl Workflow allows enterprises to automate Integrating Advanced PDF Technology with K2 blackpearl® Best Practices.
That is pretty simple. Now the next question is how should I do this?
There will be lots of things that will be done but the first step will be to create a workflow. Looking at the requirements, it becomes evident that doing a workflow in SharePoint Designer is not going to work. The problem is that the workflow is sequential and SharePoint Designer does not really work well with calling systems that reside outside of MOSS. It possible to create custom activities in SharePoint Designer to do such things as call out to a database, however this is difficult to accomplish.
At this point, that option is out. The only other option would be to create a workflow in Visual Studio. Given the type of workflow this is, making this a state workflow process would be best rather than doing a sequential.
The main reason is that the sequential really cannot handle the flow of this process because the process literally goes from one "state" to another "state".
As for the user interface, we are going to go ahead and use InfoPath. Really, InfoPath is not that bad if you are trying to shave some time off the delivery. There are tons of reasons why you may not want to use InfoPath and you can review those considerations by reading this.
In this case, the data is really flat and I really do not have any "special" user interface rules. All we need to do is capture data and use it to make decisions. Data validation rules will be extremely simple. Plus I strive to make sure that I put as little business layer logic into my user interfaces as possible.
Knowing that, there is no real good reason why I should not be able to use InfoPath. Understanding Workflows Form and Workflow Life-Cycle I have seen several examples out there where people spend the time wiring up a sequential workflow but do not take the time to explain the forms that you have and how you should use them. There is also a modification form but that is outside the scope of this. The association form will be displayed when the workflow is first added to a list or library.
This form will only ever be displayed once and will not be seen again as workflow instances are later created for content items. The association form will be displayed after you have gone through the "Add a Workflow" page.
The initiation form will be shown when a form is started. However, this form may not be seen by a user depending on how the workflow is configured for the SharePoint list. When adding a process to a SharePoint list you have the ability to say how the workflow will be initiated.
Keeping this simple, the workflow can be manually started, started when an item is created or when it is changed. The initiation form will not be displayed when a file is uploaded or submitted to a SharePoint list.
It will be shown when a user manually starts a workflow. The task form, for all intensive purposes, overrides the out of the box view of a task item in a Task List. The underpinning of everything for workflow in MOSS is a task. Whether it is a state or sequential workflow, the workflow is waiting for an event to make the workflow go to the next step in the process and nine times out of ten that is a user completing a task.
The need for overriding the task form is required because based on the state of the workflow you will want to display specific information to a user.
A task item is not scalable. Now the association, initiation and task forms are NOT the request form in my opinion. This is a big point which many people do not make when talking about how to make a workflow in MOSS. Many try to embed the request form as part of the association, initiation and task forms where they are constantly trying to get the initial data from the initiation form and then loading it back into the task form.
I think that is wrong approach for several reasons: Association, Initiation, and Task InfoPath forms only have a short life-span. They are not a form that resides in a Form Library. Once the form has been displayed and the user submits, the form is basically gone. I like this approach well because it works with content that may not be an InfoPath request form.
Calendar items, list items, pdf, etc. Both the Association and Initiation InfoPath forms can be viewed by the user once. If these forms have complex data structures repeating information you have the ability to access it.
However, that is not the case with an InfoPath Task form. You have the ability to access data in the Task form before and after the user takes action however, you cannot work with repeating data structures. Net will still be the safest bet. Set a realistic timeline This topic deserves a long detailed post on its own. This is basic knowledge for project management, but too many times have I seen projects fail because of this with or without K2.
First and foremost, set a realistic timeline that allocates enough time for technical design — so that your blueprint is properly planned before you actually start building. This gives your project a solid foundation. I find it very effective however tell horror stories relating to this based on experience. Both parties the developer and stakeholders alike should acknowledge that a tighter timeline will have higher risk for poorer quality.
A solid application means happy stakeholders, even if it means they have to wait a while longer.
Plan for Reusability Planning SmartObjects and Views smartly can vastly reduce your development time because of reusability. However, this could be a double edged sword. Forcing to reuse some Views may result in making it difficult to maintain. But if properly implemented and documented, this will create consistent development standards that will be consistent across your organization.
You can build a library for common views and objects that can be used by the entire team. Parameters can be used for Views and Forms to make them dynamic.