I have two forms from two different form library in SharePoint 2013.I want to combine both in to one form.
Can we do this in SharePoint?
Without any information about the form unfortunately I can't give you specifics however what you need to do is to have the form submit to the first document library. You can then setup a workflow on this document library that will trigger when a new file is created to create the content in the second library.
To learn how to do this I recommend reading Microsoft's introduction to workflows documentation.
Related
Or developers need the Work Item forms as designed for our agile process, but we'd like our regular users to be able to add new bugs and user stories using a simplified form, where a lot of fields are removed and some have team specific default values.
How can this be done?
The closest match I've found so far is templates, where field defaults can be defined, but the form that's used/displayed is still the large cluttered one. Being able to use the template link to land directly on a pre-filled form is a step in the right direction, though.
Azure DevOps allows you to modify your process template and add new work items to your project. You can find the documentation to do this here.
Go to Organization settings for your account --> Process --> Create an inherited process from your process template --> New Work Item Type.
You can then define the fields you want and the layout of the template.
Something else that could be useful in your scenario is the Test and Feedback Extension. This is a simple browser plugin that lets users explore feedback requests and file comments and bugs.
I'm looking to see if it's possible to integrate an existing AEM Component that I've developed (lets say button component) into the RTE.
I've read the following blog posts
http://experience-aem.blogspot.com/2015/01/aem-6-sp1-touchui-richtext-editor-color-picker-plugin.html
http://experience-aem.blogspot.com/2015/09/aem-61-touch-ui-rich-text-editor-rte-browse-insert-image.html
I've also read the documentation (which is non existent).
I'm not looking to recreate the exact same component just for the RTE, this would need us to maintain two separate code bases, recreate the custom logic we have in the already existing component which has been tested and automation.
But most of all, go against best practices as we want everything to be agnostic.
I would like to create some electronic form solution for SharePoint 2013, I am trying to explore some different option aside from InfoPath 2013, can you please recommend something alternative or better solution?
Here is a good list of alternatives to InfoPath by Mark Jones: http://list.ly/list/EKk-infopath-forms-alternatives
Full disclosure: I work for PDF Share Forms and we are featured in this list.
Choosing the right forms product can be a tough decision and you need to figure out what functionality you are really looking for. Main advantage of PDF Share Forms is that you can reuse existing forms/documents as form templates and potentially save loads of time because there is no need to design from scratch every time. Also, in the process you get a tangible document - PDF form that is not just bunch of data in your SharePoint. It is an international standard that is not going away anytime soon.
Learn more here: http://www.pdfshareforms.com/
I am searching for a way (or a case study) where Alfresco is used to perform a survey by providing a form. The Alfresco Share visitors/users fill-in the fields of this form and by submission the results are transfered to a data list, filling in the respective fields. (something similar to google forms).
Does anyone know of such a case? How can something like this be materialized? Can Alfresco forms be used this way, or do I have it totally wrong?
This really isn't a good use for Alfresco.
Alfresco is an Enterprise Content Management system that stores your content as documents, files, etc along with associated metadata and there is nothing I can see in the use case you have provided that has to do with storing documents and/or metadata.
No matter what way I look at this it is going to be difficult to create a configurable survey. Your best bet is to look to having another survey tool such as Encuestame that you can deploy to your same Tomcat container and database and then share links to your surveys in Alfresco and publish results/reports to documents in Alfresco.
You have custom dashlet for creating pools on Share Extras.
I didn't tried it yet, but I don't think you'll have problems with deploying/using it.
It not a good way of using alfresco Instead of that you will find below way usefull.
There is one web application called orbeon forms.Which is helpfull in creating web form. Orbeon provides community version by which you can test.below is the link of site for orbeon form.
http://www.orbeon.com/
Create webform in orbeon.There are 2 interface in orbeon one is form builder using which you can create web form another is form runner using which you can enter data.
Orbeon provides support for submitting data which you can change to alfresco.Here you need to put rest url of alfresco webscript
Create rest api in alfresco for saving orbeon forms.
Hope this helps!!!!!
The question was also asked in the French section of Alfresco forum in 2013. While there are "Alfresco Forms", these have a completely different meaning, nothing in common with Google Forms. As an Alfresco add-on, "Form Factor" is an answer if you have entreprise and 5.5KUSD/CPU to pay each year.
We are trying to make a document-managemnet / knowledge management portal using Plone 4. We would like a forms / structured data feature in our webapp with posibility of defining forms through the web, having workflows using these forms and being able to create reports from them (preferably in some format that facilitates simple and nice looking or skinnable printouts).
Any pointers to modules, documentation and/or literature would be great. Thanks.
Dexterity in combination with collections for reporting should get you what you need.
http://plone.org/products/dexterity
PloneFormGen is a good solution for through the web creation of standalone forms but as soon as you need your form to be workflowed, reviewed inside plone or later edited and updated then a "Content Type" is normally the most appropriate way to model this inside an CMS. Dexterity is the recommended way to build content types going forward. It has the ability to create and edit content types through the web.
For more indepth information of developing a Dexterity based solution see http://plone.org/products/dexterity/documentation/manual/developer-manual
Archetypes would be an alternative way to create content types.
Collections can be used for basic through the web reports. To make this work on the new fields in your content types you'd need to make the fields usable inside collections which I'll leave out of this explanation. For more advanced reports I'd suggest a simple BrowserView which lets you use any python you want to compose your report.
The add-on http://plone.org/products/uwosh.pfg.d2c product with PloneFormGen, is going to be the best fit for your situation.
uwosh.pfg.d2c creates content objects from your PloneFormGen form submissions. You can then use it with placeful workflows to give you a custom workflow on the submission.
If you'd rather not use placeful workflows, it also allows you to specify the content type it'll save the form to so you can have a different content type, with a different workflow on every form.
Dexterity would work too, but the TTW tool is not nearly where PloneFormGen is.
Simply: http://plone.org/products/ploneformgen