• Anonymous
  • Login
  • Register



Qenos Application Framework - Feature Request: Dependency Checker enhanced


* Dependency Checker has a new stage which ensures that component documents are responses to their respective parents. Component documents can in some instances appear to be responses but still appear as normal documents in views. This is an anomoly (bug:) in older versions of the workflow engine. In addition, components which are not tied to workflows (System parameters, View Actions & ServerScripts) are now responses to the Global Settings document, rather than to the workflow which was selected at the time these components were created. Nb. The workflow engine does not use the response hierarchy programmatically in any way. The hierarchical implementation of documents is symbolic.



Taken Actions by Owners



In this field you can enter the actual request.

You can use the rich text editor for rich text formating. You can also enter HTML to embed objects, e.g. to embed a YouTube video or a screenshot of the project. In this case use '[' and ']' to mark the passthrough HTML as such.

Please note that the first time you use the new UI your description is converted from rich text to MIME. You might want to copy and paste the raw plain text from the old UI in the new UI so that you don't loose information.
In this field owners can describe what they have done or want to do.

You can use the rich text editor for rich text formating. You can also enter HTML to embed objects, e.g. to embed a YouTube video or a screenshot of the project. In this case use '[' and ']' to mark the passthrough HTML as such.

Please note that the first time you use the new UI your description is converted from rich text to MIME. You might want to copy and paste the raw plain text from the old UI in the new UI so that you don't loose information.