Replacing system Login Count object to add user lookup — any risks?
Hi,
I want to create a report on Login Count for sales reps only. The Login Count object only has a User Name field (text type) with no lookup to any object, so I can't filter by role.
My plan is to replace it with a custom object that adds a lookup to the Users object, so I can use the User in Role object to filter by the sales role and populate the user field whenever the User Name changes.
A few questions:
- Do you see any risks with replacing a system object like this?
- What happens if Creatio updates the Login Count object in a future version, will our custom object be affected?
- Can changes to the Login Count object trigger a Business Process?
Thanks!
Like
Hello,
First, it's important to clarify that the Login Count object is not a system object - it was added either through one of the apps on the Marketplace, or as a customization by Creatio project team.
1. Do you see any risks with replacing a system object like this?
Since this is not a system object, you can replace it without issues, and everything should continue to work as expected.
2. What happens if Creatio updates the Login Count object in a future version, will our custom object be affected?
Since it's not a system object, the Creatio won't be updating it as part of core platform updates. However, if you need to update the package that contains this object, and the package's publisher makes changes to the object as part of that update, this could naturally affect your replacement. So I'd recommend being cautious with future updates to that specific package.
3. Can changes to the Login Count object trigger a Business Process?
Unfortunately, there is no functionality to trigger a process based on changes to the object itself. However, you can trigger business processes based on adding, deleting, or modifying records within this object - just not on changes to the object's structure.
Hello,
First, it's important to clarify that the Login Count object is not a system object - it was added either through one of the apps on the Marketplace, or as a customization by Creatio project team.
1. Do you see any risks with replacing a system object like this?
Since this is not a system object, you can replace it without issues, and everything should continue to work as expected.
2. What happens if Creatio updates the Login Count object in a future version, will our custom object be affected?
Since it's not a system object, the Creatio won't be updating it as part of core platform updates. However, if you need to update the package that contains this object, and the package's publisher makes changes to the object as part of that update, this could naturally affect your replacement. So I'd recommend being cautious with future updates to that specific package.
3. Can changes to the Login Count object trigger a Business Process?
Unfortunately, there is no functionality to trigger a process based on changes to the object itself. However, you can trigger business processes based on adding, deleting, or modifying records within this object - just not on changes to the object's structure.