Orbeon : Where are my forms - tomcat7

I work with Orbeon Form Builder. I had created a form with the builder interface and I had published it. Now I want to find the file myform_created_with_builderINterface.xhtml but I don't know where the path of it to edit it.
I need this file because I would like to edit and implement some XML request and I don't know how I can proceed to make it work.
Where is the file of the form that I have created before with the builder?

The published form definition is stored in a database when you save or publish it.
If you haven't made any changes to the Orbeon Forms configuration, form definitions and form data are stored into the built-in eXist database, whose files are under WEB-INF/exist-data.
If you have configured a relational db, form definitions and form data are stored in one of the database tables: orbeon_form_data for non-published form definitions and form data, and orbeon_form_definition for published form definitions. In both cases, look at the xml column.
The cross-database way of retrieving it though is to use the persistence API: an HTTP GET at the right URL will give you the form definition, provided the service has been open or secured.
I am still unclear why you need this "to edit and implement some XML request" though. Better work with the source of the form definition, which you can see in Form Builder's Edit Source, or using custom model logic.

Related

Quick Create Form is not appearing in dynamics CRM

I've created quick create form of a custom entity ABC. In entity properties, I also enabled Allow Quick Create Form. Lastly, lookup of parent entity is also placed on the form and marked as business required.
In normal interface, I can confirm that the quick create form is populating without in problem. But unfortunately quick create form is not populating in unified interface.
Any idea why the quick create form is not populating in unified interface?
You have to add the Quick create form in the UCI app assets.
Read more

How to build a simple form in CQ5

I have started a new AEM project in eclipse that has
core
launcher
tests
ui.apps
ui.content
I have a local instance of 5.6.1 running and I would like to create a very simple form (firstname, lastname) and have it persist data such that I can view data for all forms submitted. Also, I would like for the form to be approve/rejected (e.g. user1 submits the form, user2 accepts/rejects it).
I'm new to AEM and have been looking at docs and trying to find a tutorial for it for a while now but haven't been successful.
Question
Can someone please walk me through how to accomplish this simple form? Once I can do this I can build-up more functionality on my own.
What I've tried
I tried to create a form in the Geometrixx Media site but I don't see form template there.
I also tried following this tutorial but it didn't help since its for 6.0 and is confusing to the point that I don't follow it at all.
You need some basic understanding of how cq/aem works in order to accomplish the task you started. But in the simplest use case, you need the following things:
You can create new cq page component and define in the jsp the html markup of the form you need
Or you can build a page/component using the /libs/foundation/components/form components. Start reading the best from the page developing forms.
The form action can point to the component itself where you can store the data (if you create a page with a component who is responsible for rendering the form) and in this case you can let sling post processor to handle the data storage or you can define your own action with a servlet where you can create a node on your desired location.
The second part of you question is about approving/rejecting submitted data. I guess, that you are talking about workflows. Every time the form is submitted you have to create a new node (or let sling to create it) and than start a workflow for moderating the content. You use here as example the implementation of the social comments and the moderation workflow.

creating a simple settings form in joomla 2.5 with JForm

I am newbie to joomla! component programming. i am creating a MVC component that users can reserve some dates.
my component should have a simple settings view that admin can manage the component.
i used some references but i have problem to create this settings view and it doesn't work.
to do this, i created a #__mycomponent_settings table and a row that holds settings data and also added these files:
com_mycomponent/controllers/settings.php
com_mycomponent/models/settings.php
com_mycomponent/models/forms/settings.xml
com_mycomponent/tables/settings.php
com_mycomponent/views/settings/view.html.php
com_mycomponent/views/settings/tmpl/default.php
I defined my fields in the xml file and loaded them to the view correctly, but the real problem that confuses me is i really don't know how to use JForm and JTable correctly to submit and save data in the database or to retrieve previously saved data and put them into the fields. or how i should use JToolbarHelper to submit data or what must be entered in the action attribute of the form. i used save button of JToolbarHelper but it takes me to the
com_mycomponent&view=settings&layout=edit
but i didn't define any edit layout everywhere in me code!
i get so confused and will be appreciated if you help me.
I'd strongly suggest using native joomla settings logic, instead of storing them on database.
You can read more about it here http://docs.joomla.org/J2.5:Developing_a_MVC_Component/Adding_configuration (read only the Adding configuration parameters part
If you have more questions implementing it, I'll be happy yo help.

what is the correct approach in order to host / integrate / show my existing MVC3 project inside orchard?

I've an existing MVC3 project that implements a certain functionality, this project has it's own views, and a separate Database.
now I'm required to use the same functionality inside one of my orchard project,so I thought that I can host this solution in somewhere and view it inside an iframe or something.
Am I thinking right?,
is this the correct step to take in order to achieve this requirement inside Orchard?
to make it more clear, all I need to do is to view this solution and interact with it's controls and views from a hosting page inside orchard, and the subsequent requests should be handled by my solution in order to hit it's own data store and get back with the requested data in order to be displayed to the user.
any help would be appreciated.
Update:
thanks for Bertrand Le Roy for his answer, I can now view my solution inside my
orchard website.
I came in to one more HUGE problem, which is that my application can no longer connect to my external database.
I've a DB that is hosted in some where else, and I'm using EntityFramework to deal with it.
the problem is that if I put the connection string inside my module web.config, or main orchard web.config, I run into several types of errors like:
"System.Reflection.TargetException: Object does not match target type."
or
"System.Data.MetadataException: Unable to load the specified metadata resource."
My question is: How could I pass my connectionstring correctly to my solution, assuming that I'm using Entity framework as my ORM.
Many thanks.
You will need to put it into a module.
You will have to move route definitions to a Routes.cs file (look at any existing such file for examples).
You will also need, in order to access your data store, to opt out of the ambient Orchard transaction around the data access code (using (var scope = new TransactionScope(TransactionScopeOption.Suppress))).
If you are using dependency injection, you may have some work to move that to the Autofac-based way of doing things in Orchard.
If you want your work to appear seamlessly in the Orchard admin, you may want to decorate your admin controllers with the Admin attribute. If you want your front-end to use the current theme, you'll have to add Themed attributes and maybe refactor your views so that they only emit HTML for the content zone instead of for the whole page.
Add a manifest (module.txt) to your module folder and you should be good to go.

Dynamics CRM Managed Solution Add Customer Set Parameters

I'm creating a solution which will be released as a managed solution for Dynamics CRM Online.
However, the customer will need to put information in when installing the managed solution to allow interaction with outside services.
For example, when you install the LinkedIn solution, you need to add your log in information to allow the CRM to access your LinkedIn account.
How do I add these parameters to the a solution, and then allow the customer to update them if they change?
Cheers
Edit:
To add to my query and following the answer below.
To make sure the process is correct in my head.
Option 1.
I will create a custom entity for storing key/value, or username/password combination.
I would then create a customisation page for the solution using html web resource, which when submitted, javascript would create a single record to hold those values.
I then need to link every record that needs the values stored in the custom record - I'm not sure how this would be done without editing a workflow after the storage record has been created, to link each normal record to the storage one.
Option 2.
Create an xml web resource that stores the values. Create the html/javascript resources to update this using the configuration page.
I can then use a javascript function to obtain that data when the custom entity is created, perhaps to populate hidden fields for storage and use behind the scenes.
I can't find any tutorials on getting started with using xml in this way - can you point me in the right direction?
I typically create a "Configuration" entity that has Name/Value attributes. This is also useful when you have Dev/Test/Prod environments that require different configs (e.g. URLs, credentials, etc).
Another approach is to using Plug-in configurations or Web Resources to store that type of information. The Plug-in configuration is pretty straightforward if you can have the customer use the Plug-in Registration tool to modify the value.

Resources