Hello,
we are looking into measuring how much items/modules are beeing used by our users.
I think if you add a client method to a item, that should be no problem with an OnShowItem event and then increase a number on a table somewhere.
But is there are global approach that we don't have to insert such a method in each item we want to track?
Any ideas are welcome,
thanks in advance.
Hello
Go in the Main Menu in the Top right, then click on Help
Search for "Configurable History" and hit enter key
You should find all information you are looking for:
In particular this:
Thank you very much.
I think this is feasable for our older standard items, which use the normal forms.
But we are transitioning into ProAppDesigner, which use their separate viewforms, which are not triggered by the "FormView" action available in the History template.
Do you know, if there is a way to write a custom action for the history?
Hello
History actions are hard coded, and I'm not sure if you can register new action.
I think you will have to create your own Access Log, using ProAppDesigner server call like View Load.
May be some one will have more experience than me on ProAppDesigner and will guide you better.
Keep us posted, I'm interested on how you will achieve this.
Hi,
many thanks for the history idea! I didn´t know that there is a FormView or even FormPrint option! I had a similar question in the past where these functions would have been useful!
https://community.aras.com/discussions/development/what-is-the-best-way-to-secretly-observe-my-users-to-see-if-they-use-specific-it/8510
An alternative idea to address the use case in this thread:
In our company, we use a "trophy" column in the part list that indicates how often a part is used. It was initially introduced to help eliminate duplicates. Today, it´s mainly used to help users find commonly used parts. After all, why use something exotic when you can use what everybody else uses?
For the use case above, OnShowItem could trigger a Method or SQL procedure (would avoid an history entry!) that updates the counter. Simply solution that can be removed easily once it´s not needed anymore. But it requires some coding.
Hi Angela
I like this Trophy concept. this can be useful in particular when your Item is a Requirement, a Document or a file. I'll keep this in mind.
for the Part itself, I think a kind of counter based on BOM and Quantity may be more relevant. This can help to suggest user to select the most used Part.
I can imagine an attribute with value list "proposed", "recommended", "mandatory" and that user may have to record a justification when not using the recommended or even needing an authorization for deviation when not using the Mandatory.
