Documents in the release notes:
Example:
$('#nameOfPage').trigger('create');
Quote:
New "create" event: easily expand all widgets at once
As long as the page plugin no longer calls each plugin, it dispatches the "pagecreate" event, which most widgets use to automatically initialize itself. While the widget plug-in script is referenced, it will automatically improve any widget instances it finds on the page, as before. For example, if the selectmenu plugin is loaded, it will improve any selections that it finds in the newly created page.
This structure now allows us to add a new creation event that can be triggered on any element, saving the task of manually initializing each plug-in contained in this element. Until now, if a developer is loaded into content via Ajax or dynamically generated markup, they must manually initialize all the plugins contained in it (list button, select, etc.) to improve widgets in the markup.
Now our convenient create event initializes all the necessary plugins within this markup, just like the page improvement process works. If you want to use Ajax to load HTML markup in a block (for example, an input form), you can automatically create an automatic creation, convert all the widgets that it contains (inputs and buttons in this case) into advanced versions. Code for this script:
$( ...new markup that contains widgets... ).appendTo( ".ui-page" ).trigger( "create" );
Create vs. Update: An Important Difference
Note that there is an important difference between the create event and the update method that some widgets have. A create event is suitable for improving raw layouts containing one or more widgets. update method that some widgets should use on existing (already enhanced) widgets that have been processed programmatically and you need to update the interface to match.
For example, if you have a page on which you dynamically added a new unordered list with the data-role = listview attribute after creating the page, initiating the creation of this list in the parent element will transform it into a list-style widget. If there were more list items then with programmatic addition, calling the view list update method, update only these new list items in the expanded state and leave the existing list items untouched.