I amd new in people code , creating one application in which we need to transfer variable from one peoplecode page to antother page containing HTML area. When i am trying to do the same i am getting blank page.
You don't need to transfer variable values from one peoplecode event (e.g. page1.activate) to another (e.g. page2.activate).
First and better solution: Assign your html area object to a component record field and you can access its value within context of your component.
Another solution: Declare a variable at component level
Related
I am trying to develop an interface that binds to a complex backend model. What I need is a way for scripting to enable me to have a page load different page fragments based on what list row a user clicks on. As an example, on the left side of the page there would be a vertical list displaying different sections in a large assessment 'document' (mental health assessment) (each section would be it's own data model [e.g. presenting problems family history, trauma history, etc...). In the main section of the page to the right, you would have room for a page fragment or some type of container that would contain the actual page or page fragments associated with each section listed in the list on the left. When you click on the section name in the list to the left, scripting would be able to have the correct page fragment or page loaded inside the container.
The data model needs to be this complex because there are multiple types of "documents' and the system needs to be able to dynamically load a list of document sections and allow the user to load the form for each section type.
THIS IS FROM Markus Malessa: The dynamic page content is definitely possible, however since it sounds like a lot of your items are going to be based on hard data, the models really are not dynamic, so you really can't build in dynamic data at run time for example. Rather than visible/invisible properties I might suggest navigating to different pages instead and maybe having many-to-many relations to your list item and if your list item has OldFamilyHistory and NewFamilyHistory data relations incorporate a popup to select which page you may want to navigate to.
I am trying to let an info part's dynamic link work so that it only opens the queried values in a list on the new form.
Basically now, if i click Installation No. on the form part below.
Then this form opens up with all the Installations, not only the related Installations.
What i want to happen is when the Installation No is clicked then the list should look like when the "more" button is clicked or like the image below.
It seems like this is the standard function but i want to know if there is a way to change it.
Does anyone know a solution to this or know if there is any?
Dynamic links should work on info part forms provided prerequisites are met:
A data relationship exists between two tables, usually as one-to-many (one parent row relates to many child rows).
Each table has a field of the same extended data type.
In the parent table, the extended data type field values uniquely identify each row.
The extended data type has a relation defined on it for the field in the parent table.
Each table is a data source for one of the two forms.
The parent form contains a button that launches the child form.
I have a Cognos report and i have created 3 pages and 1 common prompt page. According to a radio selection in the prompt page i show the appropriate among these 3 pages.
In each page i have a block that is the header and there i just show title, current date and the selected values of the prompt controls (parameter values).
This header is the same among all pages and i want to find a way to create only 1 header section and then assign it on the top of each page. So if later i want to change anything in the header i will do it in one place.
Any ideas?
Re-using parts of a report (either from the report or other report in Cognos Connection) can be achieved with the help of layout component refenrences which are inserted into your report page and which refer to other existing components.
To use them proceed as follows:
Indentify the layout component(s) to be re-used (e.g. a table or a text or more or less anything less).
In the property list of that component go to the name and give it a unique name.
In the report page that is supposed to re-use the component drag an instance of the layout component reference to the appropriate location in the page.
Specify the target of the reference by choosing the report and within the report the named component (same name as given above).
Example
A block component (which could be incorporated into a header) is to be re-used. Give the block a name, e.g. my_block:
From the toolbox drag the layout component reference
to the report page. A dialog box opens which permits choosing the target component:
If I have a set of image (buttons) or even just plane images, 5 in a row, and I want to achieve the following, what would be the easiest way, I can't realy find a good solutions to this:
On clicking either of the images, it needs to get a new src, but others need to be restored to the original state.
A Asp:Label needs to be set on clicking, based on the image clicked
On doing a PostBack, I need to know which one is selected
Asside from this, it's asp.net 4.0, so single quotes are giving me javascript pain.
On clicking either of the images, it needs to get a new src, but others need to be restored to the original state.
First of all you have to create a function in which you will set all 5 images to the original state.
Then be sure to give same class name to each image element.
After that crate a function which will fire according to class name like
$(".classname").click(function(){
//first call the function which will set all 5 images to original state.
//then change the source of the current image. onwhich user has clicked as below:
$(this).attr("src","new source");
// here you can store the id of current image in a variable to keep the record which images have been clicked
});
A Asp:Label needs to be set on clicking, based on the image clicked
you can easily set the Asp:Label in above function. If you are familiar with javascript code. Its too simple to set.
On doing a PostBack, I need to know which one is selected
After creating the first function your rest of two steps get completed them selves.
in above function you have saved the IDs of images on which a user has clicked in a variable.
on doing postback you can easily save the varibale's data in hiddenfield or assign it to static varibale or what ever the way you like.
at last you can access it in code behind.
If i have to do this thing. i'll follow the above process. Its far easy and fast process. Everything can be done at client side.
what you think?
I've set up an application to print the current state of the control I'm using (in this case an ArcGIS server map), but I'd like to set up a print function that uses it's own template to print rather than grabbing the state of the application.
I've attempted to do this by setting up a flex component that lays out the items I want to print and instantiating it when I call the FlexPrintJob. Unfortunately, simply instantiating it results in getting a blank green square.
There are two main questions about this that I'd like to put out there. First, what needs to be done to print a newly instantiated template rather than just grabbing already existing controls from the screen? Second, for more controls that need to load complicated data from multiple sources, like an ArcGIS map, is it possible to instantiate them in that kind of environment, or is there a way to take an image of the control in the application and print that?
I found that the best way to do it was to use the ImageSnapshot.captureBitmapData() method to get an image of the map as bitmap data, and then, if necessary, clip it into another BitMapData object using the copyPixels() method.
Once I'd done that, adding the template to the print job was simple:
Application.application.addChild(printTemplate);
printJob.addObject(printTemplate,FlexPrintJobScaleType.SHOW_ALL);
//printJob.printAsBitmap();
Application.application.removeChild(printTemplate);