Doubts with BDM use
Hello,
I have used Bonita 5.10, and now I'm starting with Bonita 7.3. I have testing the BDM, but I have some doubts:
-
BDM replace the use of any other external bd with his own model? I have to implement some processes for notifications management (register, management, execution...), and I will need consult this notification from an external page through API. Using only BDM I can store all data asociated with notifications?
-
I have done some tests with BDM, and I have created new objects, but I dont know how delete these records. Is not possible delete BDM records? Because if it is not possible, the BDM is not useful for me.
-
I have some doubts about if BDM is valid for the master data management. If I want several tables which store the possible values for forms dropdowns, Is valid the BDM for do it? If it is, how these data would load?
I have many doubts about the approach and operation with BDM at Bonita 7, so if someone have used it and could help me...
Thanks and regards
The use of BDM does require a brand new way of thinking and, I'll be honest we're still working at it as 90% of our working is with external DB data. We use AJAX extensively now because of BDM compared to 5 and 6 implementations.
5 and 6 were much easier to use as it was fully integrated with external DB, we find 7 much more difficult in this respect.
1) (Does) BDM replace the use of other external DBs?
Yes, and No. The Getting Started Tutorial gives an example of a travel request that is built as a BDM. But with 2,000 people asking for travel requisitions every day is this a valid use of BDM. Absolutely Not. We use external DB all the time as it is linked to our HR system (OrangeHRM).
However for people without an external HR system and who only have 5-10 requisitions a month, it's perfectly fine...
It depends on your implementation requirements, simple as that.
2) Can we Delete BO? "IsDeleted" is such a strange phrase, I read it as a question not an Action, "willBeDeletedAtTaskEnd" would be so much better to understand. :)
3) BDM as Master Data
In comparison to @contact_420's answer this is where we use BDM extensively. All our static data has approvals to go through and it doesn't change much. We also have compliance requirements to keep copies of old static data.
All of our static data has their own process for CRUD, so for example Country has it's own process (and any associations such as County, City, Town etc.)
When we update a BDM for Static we have Release Dates, Active markers etc. to enable us to determine the correct BDM to use at any particular time.
It depends solely on your need, you must decide.
regards
Seán
PS: If this reply answers your question, please mark as resolved by ticking the tick mark on the left of this reply.
Hi,
I'm not sure what you mean in the first question, but can answer other ones.
You can delete BDM. Operation 'isDeleted' is probably what you need - http://documentation.bonitasoft.com/?page=operations
And about BDM as the master data management - it can work this way, but it is not what it is designed for. To store/manage such 'static' values like dropdown values it would be better to use another database.