David
I'll take a shot:
- lets say you have 2 entities, Player and Team.
- Each entity has 1 attribute, Name
- there is an association between the 2 such that each Team can have many players and each player can have only 1 team
- on a Player new edit page, you would have 2 entry fields, Player.Name and input reference selector for the association pointing to attribute Team.Name
- if the user types in a team name that is not in the database, the widget will create a new Team object with the Name entered by the user, populate the reference between Player and Team with the newly created object, and then invoke the Not Found Microflow and pass in the Player entity
To accomplish what you want, I think your microflow should have the following Activities:
- Retrieve the Team object from the passed in player via association
- Delete the Team object (Deleting the Team object should empty out the reference between Team and Player)
- Display a message box that the team entered does not exist, and instructing the user to try again
Is this similar to what you have tried? If so, what results did you get?
Mike