Using Sprint 12
- What are variants and constraints, and how do I use them?
- How do I create links between entities?
- Is there any way to create a re-usable class or type. For example, I have residential address, postal address, and previous address, all of which look like an address? Is there any way to create an address type, like you can in XML schema?
- Why does an entity need to be persistent, and have an id property, in order to be used within a Guide? Surely all we’re really doing is effective creating an XML schema?
June 17, 2009 at 5:45 am |
“links” between entities are really only about “Collections” as far as I know. So if you have an Entity called “Company” it might have an Array List of “Employee” entities. This implies a 1->many relationship between “Company” and “Employee”.
June 17, 2009 at 5:49 am |
A “Persistent” entity is one that will be associated with a Service to perform CRUD operations on an instance of that entity. Such as “findEmployeeByID()”. I was told by Andy that all entities used by Guides are persistent and therefore they must have an ID attribute. To be honest I don’t quite understand that myself yet as the model could be used in memory at run time only. But he told me it has something to do with the fact that an instance of the model can be serialized into XML. OK I;m just making it more complicated now!
June 17, 2009 at 5:52 am |
If you author and FML and deploy it as part of your application, you will actually get new string Types available to you in process development just like “User” for example. This gives you a way to introduce new custom Types to the system and use them in processes. That becomes really useful if you want to expose an LC application to be called from Flex and use the same Types in your Flex project too.