Creating enabled applications

Question

Hi, I would like to ask if this is correct behavior of the application - I'm creating AOBApplication object in the custom script using PropertyBag but application is created as disabled, while using other approaches object are created correctly. Please look in the test code below 
 Public Sub CreateAOBApp()
	Dim a As IEntity = Session.Source.CreateNew(Table.AOBApplication)
	Dim b As IEntity = Session.Source.CreateNew(Table.AOBApplication)
	Dim c As AOBApplication = Session.Source.CreateNew(Of AOBApplication)()
	Dim bag As New PropertyBag()
	With Table.AOBApplication
 bag.PutValue(.Ident_AOBApplication, "Application A")
 bag.PutValue(.Description, "Created by bag property")
 bag.PutValue(.IsInActive, False)
 bag.ChangeEntity(Session, a, True)

 b.PutValue(.Ident_AOBApplication, "Application B")
 b.PutValue(.Description, "Created by IEntity")
 b.PutValue(.IsInActive, False)

 c.Ident_AOBApplication = "Application C"
 c.Description = "Created by AOBAppliction object"
 c.IsInActive = False
	End With
	a.Save(Session)
	b.Save(Session)
	c.Save(Session)
End Sub 
 and result in the Manager

It was tesed on One Identity Manager 8.2.1

Markus Weiss-Ehlers · Accepted Answer

Hi Marek, 
 the behavior of the property bag is by design and cannot be changed without breaking backward compatibility. The Entity in Delayed Logic mode (Default) already behaves similarly to a property bag of the old SingleDBObject in writing all properties end executing all templates at the end during the save operation. Therefore a property bag should not be necessary while using entities and should be replaced by normal property assignments (as you did already). HTH

Creating enabled applications

Top Replies