Export procedure steps detail / cube/entity information to excel

Shinji Shimosato · 2023-08-03T08:23:31+00:00

There was an error rendering this rich post.

Many our customers would like to have a function to export board setting information to excel like procedure step deitals , cube sturucture, entity info etc.

They would like this fucntion for document purpose. If we have this funciton, they can create system document easily and this would improve maintenance quality.

Find more posts tagged with

Archived

Status: Archived

Comments

Daniel Borghs

Hello @Shinji Shimosato,

just a suggestion from my side. For an in-application documentation(replacing an external "paper" documentation) we in most cases create a procedure calles #documentation# or similar. Its purpose ist not to be run but to only to be read for reference purposes.

Within the documentation we include groups for Cubes, Datareader, Entities or whatever we feel needs to be documented. Within the mentioned groups we create e.g. for each cube one procedure step "align cube" and we input the purpose/documentation for this cube in the comments fild to the right of the "align cube" step within the same line. This way you can create a list of cubes with a comment for each.

The same can be done for entities, datareaders, procedures…. just make sure you dont include any "goto group" actions in the main group so the "documentation groups" can never be reached and executed by board in case someone presses "run".

Procedures can be documented within the procedure editor. We generally use the comment field of the first line of each procedure to briefly and concisely state the general purpose of the procedure. More complex operations are documentet within each of the procedure lines.

Also it could be a good idea to review the capabilities of the object analysis and impact analysis features within each board database.

Most of our customers appreciate this kind of in-app documentation and don't necessarily need more paperwork. Of course this concept is very basic but at the same time it is simple to handle. I'm sure you could come up with even more ideas to improve on it.

Regards, Daniel

Peter Foulkes

Related idea here:

https://community.board.com/discussion/16364/integrated-technical-documentation-functions

Product Management Team

Thank you for sharing your idea, @Shinji Shimosato.

We appreciate the time and effort you put into crafting your suggestion, and we understand that it can be disappointing to hear that we won't be pursuing it at this time.
We are committed to delivering the best possible experience to our customers, and we must prioritize the features and enhancements that will have the most significant impact on your daily use of our software.

While we won't be moving forward with your suggestion, we want you to know that we value your input and appreciate your contribution to our community. We encourage you to continue submitting your ideas and suggestions in the future, as we are always open to hearing new perspectives and feedback.