0 Followers
Follow
|
3 
Promote
Demote |
Please bring back LiveCycle Data Services ES Express. A licence that lets you use the full version of LCDS in production with this limitation: you have to deploy the LCDS on a machine with a single CPU (a multi-core CPU is counted as a single CPU) and a single application.
"I can think of a lot of applications built for small and medium intranets (CMS, mini ERPs and so on) that probably can be run successfully on a machine with a single CPU. And if the application grows over time, probably your client grew as well, and now they can afford to buy a license for multiple CPUs (they had the chance to test the technology and see its value gives and what problems it solves)" -adobe evangelist-2008
|
|
|
|
|
3
Promote
Demote |
It would be good idea to provide some API in Mosaic service using which Mosaic service can register to Mosaic message/events in same way as a Tile can do.
|
|
|
|
|
3
Promote
Demote |
LiveCycle Mosaic is a great platform for taking Flex RIA in Enterprise world. Organizations use SAP Portal as these Enterprise Portal or for atleast for most of the SAP application. Those RIA Portal on top of existing Portal would make more sense to both IT staff and Management. This combination would also allow easy User Role Security which is supported by Mosaic as SAP Portal provides good interface for roles, Groups and other security management.
Also considering the fact that Mosaic allows development of small Tiles and deploy them Quickly and also SAP Model driven development in LCDS enterprise can quickly help deploy small application and PoC. Which will drive RIA adoption in Enterprise.
|
|
|
|
|
3
Promote
Demote |
Our applications have many instances of DataService in use at the same time, managing different destinations.
We want to use commitRequired property for objects from a specific destination only. Our Save button appears only when commitRequired is true.
However, commitRequired shows up true (and thus our Save buttons) on EVERY display where managed objects can be edited, even for DataService instances that are responding to completely different destinations...
This is very misleading to the end user... This would be like having all of your MS Word documents open simultaneously each showing changes made after editing only one document.
I understand the shared DataStore concept, but pending changes should be associated somehow with a particular DataService, to keep them isolated from each other during editing, and commit().
|
|
|
|
|
3
Promote
Demote |
LCDS Sequence Manager can infinitely loop and the server can remain unresponsive until restarted when data records in the database are inserted or deleted outside of LCDS, or record sortation changes for a given set of fill parameters.
This Data Services enhancement request calls for full support of the use case where data may change outside LCDS for paged and non-paged destinations. LCDS would simply notice the inserts, deletes, or sort order upon the next fill request which returns, or does not return, the records inserted or deleted, and would handle it gracefully instead of going into an infinite loop.
Here is a list of reasons why data could change in the database outside of LCDS: 1) LCDS could be used for "webfacing" a legacy application, 2) SQL statements could be issued by the DBA, 3) database system level functions may exist such as stored procedures and triggers, 4) Java or non-Java middleware from third-parties (with no source code) may be required, to support non-Flex cl More...
|
|
|
|
|
3
Promote
Demote |
In a custom client additional attributes for routes can be neccesary. E.g. a route type which is just defining which icon the client should use for a route. Another sample could be a level of validation which needs to be met, or any "Are you sure" popups for very sensible routes. In our specific sceneario we need to define for each route of a task if a user selection (single,multi,possible users/groups) is necessary at the time of submitten a workitem using this specific route.
To be able to handle route specific logic in a custom client, the client needs to get additional information about the route. Currently there is just the route name, which could be abused to get some additional information in it (e.g. Submit|validate|multi). The more comfortable way to provide this information would be one or more additional attributes for a route which can be defined in workbench. This attributes needs to be provides in The workitem synchronisation to the client.
Currently only the possible r More...
|
|
|
|
|
3
Promote
Demote |
Currently a route got one property called name. This property is used for 2 things:
- Identification of the route (used in communication)
- Button Text in Workspace for route selection
For those 2 things seperate Attributes should be used. One for identification, one for a language dependant definition of the UI visible Buttontext in Workspace.
Espacially in a custom development scenario (with a custom client) this gains importance, because you are identifying routes and maybe display another icon for special routes. The only chance to identify the roue currently is it's name. But names might change during a project. IDs could stay as they are.
|
|
|
|
|
3
Promote
Demote |
A function to validate all processes in one action. If you have lots of processes and custom components every parameter modification can affect a list of processes which call the modified function. A validate all function could help to quickly identifiy all processes which call the process/function.
|
|
|
|
|
3
Promote
Demote |
Possibility to find Processes which use the current shown process to identify dependencies easier.
This function should be comparable to "References" function in eclipse which exposes all souce lines which a calling a specific function.
|
|
|
|
|
3
Promote
Demote |
LC Designer should have an easy way to show Required fields marked with a Red Asterisk. This is a very common standard adopted by all onine forms, why isnt this in designer? Infact this very form I'm typing in to make this post has this convention! The Livecycle Cloud solution called Form Composer has this, Designer should have it too.
The current solution of having a red border is not very conventional that aesthetically pleasing.
|
|
|
|
 for LiveCycle ideas.
|
|
| Technologies |
| Categories |
| Tag Cloud |
attribute blazeds bug certificate custom data database datamanagement dataservices digital dms email encryption etl events find flex forms language lcds licencing linux livecycle livecycleds mac management mosaic osx output parameters portal pricing printing process property public purge reference ria rm route sap service services signature subprocess synchronisation validation workbench workspace xml
 0.95197 seconds |
