Appian Designer logging

RE: Appian Designer logging

Timo — Thu, 03 Sep 2020 06:07:54 GMT

Yes we do exactly the same

RE: Appian Designer logging

Jake — Wed, 02 Sep 2020 13:56:11 GMT

Its not forced but as a best practice we have a change log at the top of all expression and SAIL using /* */ comments. CDT, Constants, DS don't get comments. Process models get comments in a note. In the comment we enter date, user, ticket number, and high level change for tracking purposes. Actual comments on execution go inline with the code as you would in any language.

RE: Appian Designer logging

Stewart Burchell — Tue, 01 Sep 2020 13:34:50 GMT

Appian Objects have versions, you can always go and look at the latest version and compare it to previous versions to see what has actually changed. You can also educate your developers to get into good habits to comment their code - both in a 'standard header' but also in-line with the code they're changing.

RE: Appian Designer logging

Mahantesh Suryavanshi — Mon, 31 Aug 2020 13:21:05 GMT

Yes, But it is very much helpful when multiple developers are working on a single object - Inorder to understand the latest changes made by the other developer.

RE: Appian Designer logging

Stewart Burchell — Thu, 27 Aug 2020 08:39:59 GMT

Objects have a 'Description' property, and you can add comments within the object definitions themselves but, no, there is no 'forced comments' capability. Like any such functionality forcing them to add a comment does not ensure that the comment they add is in any way meaningful!