Dynamic recursive destinations
KB000036
PRODUCTK2.net 2003
LEGACY/ARCHIVED CONTENT
This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.
| The following article has been replaced by the articles listed below. |
| ||||
| KB000051 - Setting activity destinations when the destination users are not known | ||||
| It may happen that the destination user for an activity is not known at design-time. By design, K2.net will not allow a process to be exported if there are client events within an activity, but no destination rules to couple with these client events.... | ||||
| KB000161 - How to use a string table value in a destination rule for deployment across environments | ||||
| Introduction. Improper design practices can limit the success of any solution. It is imperative that the developer understands the various factors that affect a K2.net development project in order to ensure proper system performance and scalability. Contained in t... | ||||
| KB000161 - K2.net Process Design best practices | ||||
| Introduction. Improper design practices can limit the success of any solution. It is imperative that the developer understands the various factors that affect a K2.net development project in order to ensure proper system performance and scalability. Contained in t... | ||||
