I've just started in FM 14. I have a client table and a project table. When I look at a client entry I have a portal that shows me the titles of the projects they have commissioned. I'd like to be able to click on one of the projects in that portal list and be taken to the layout that contains all of the other fields in that project record. Can this be done? Is this enough information?
Yes. Set the button action as a script step "Go to Related Record". In this script step, set the table as "projects" and select the layout you would like to go.
I would stay away from GoToRelatedRecord. I usually just grab the ID from the item in the portal, then search for that item on a new layout, then do whatever I planned on doing. It's safer. With GoToRelatedRecord you can never really control what happens.
Related
I'm making an app for authors using Filemaker. I posted this question on their forum but still haven't gotten an answer.
My app is basically a place where people can keep track of all the details that go into creating characters and locations. In each book (record) I have a tab control with 4 tabs: Book Details, Character List, Location List and Group List. Within the character list tab I have a portal which shows a list of the characters for that book.
I'm trying to create a button for each row in the portal which takes me to that records details page (the one with the red box around it). Right now, it's set to go to the character details layout. However, whichever row I click on, it takes me to the last visited record. Is there a way to go to each row's record from the portal? If not, do you know of a way to do the same thing through another method? I have a list layout which I used before, however, it doesn't hide the records for different books. For example, if I select book 1, it still shows characters for book 2. Thanks in advance for any help you can give me!
Create a button, attach a script or single command that uses the Go To Related Record script step using the same relationship as the portal.
Make sure the button fits within the row.
I have two tables: Users and Tasks. Each User can have many Tasks but every Task can have only one User.
If I click on John Smith in the first layout I'll be taken to a new layout that shows me only John's tasks (thanks to "Go to related record" script).
Now, what I'm trying to accomplish - and need some help with - is from this layout I would like to be able to see a scrolling list of all John's tasks on the left (but only their titles). When I select, say, Task 20 I want to see all of Task 20's metadata on the right. In other words, a master-detail view like this:
I followed this video tutorial​ which got me close to my goal but not all the way. If you skip to the 6:20 mark you can see what he does. But basically his approach is this:
From the Contacts layout he creates a portal.
He creates a summary field called listOf and chooses to create a "List of" IDs from the Contacts table
He creates a relationship from the ID field and the listOf field
He populates the portal with this data
He uses a script to "Go to related record" when the user clicks on a button in the row
This approach works great for the master-detail view, but it has one problem for me. I don't want to see all tasks, just John's tasks (or whoever I clicked on in the previous layout).
Not sure how to solve this. Do I need to create a "Constrained found set" when I navigate from John Smith's record in the previous Users layout?
First, I would have a standard portal on the left, using a cartesian join to show all records, or you can use this technique with the summary field if you wish, but it is not necessary.
Then add a filter to the portal to only display records with the same User ID as the current record. This will accomplish what you need.
I'm working on a project that's got a great JIRA setup and awesome buy-in of everyone for the agile development process. The issue I'm having is that tickets stack up in code review. I'd like to be able to see who code reviewed what, much like I can see who has closed out which tickets.
I know that metrics are there to be used for good and not evil, so I want to do this to ensure that people spending time code reviewing are properly credited instead of that time not being recognized at all.
Currently, everyone who does code review assigns themselves to the ticket (which is unassigned upon being placed into the "Ready for Review" workflow state), so at some point there is a record of them working on it. Is this a good way to track the reviewers and is there a way to get aggregate information this after the fact? If not, is there a better way of representing this information in JIRA?
Thanks!
A simple solution would be to add a custom field called 'Code Reviewer' of type select a user. You would be able to search on that and report on it.
You could workflow it so that when the issue is transitioned out of your 'Code Review' status a window pops up containing only the "Code Reviewer' custom field to be completed.
What you need to do:
Create a new custom field - this is done in the 'Issues' configuration menu. Ensure your custom field uses the 'select a user' type.
https://confluence.atlassian.com/display/JIRA/Adding+a+Custom+Field
Create a new Screen - this is also done in the 'Issues configuration menu. On your new screen you need to make sure that the only field that is visible is your new custom field.
https://confluence.atlassian.com/display/JIRA/Defining+a+Screen
Edit your workflow. Find the transition from out of 'Code Review' and associate it with your custom screen.
https://confluence.atlassian.com/display/JIRA/Configuring+Workflow
The result will be that when a user transitions out of 'Code Review' they will have the custom screen pop-up. They can then select the name of the person who did the code review and this will be populated in the custom field.
Let's say that I have a vast quantity of restaurant reviews in a database -- not Joomla articles, just database tables. I want to display these restaurant reviews as part of a Joomla 1.5 web site.
I can write a component to display each review. That part is fine. But rather than listing the reviews as a list on a page, I want to use the nice cascading menu that is part of the Joomla template that the site uses. But I don't want to have to add menu items one by one for each review; I want menu items to be generated automatically from the database contents. The menu of reviews should 'plug in' the existing menu structure for the web site (i.e., I want to supply the code that generates the menu items with an existing menu item so that it generates itself under that item).
How can I create code to programmatically create that menu? Component, plug-in, module, ...? Would the menu be generated at page display time, or "manually" in the admin panel (I'm ok either way). Any examples of this already?
I think the simplest way would be to create a custom menu module. The absolute basic one would just output the list of reviews in a <ul> and then use some css to style the list.
I ended up creating a component that creates the whole menu structure at once, upon admin request. It just creates rows in the jos_menu table, as if the menus were created manually. Updating the hierachy is a pain (and I haven't completed that part), but creating the structure from scratch is pretty simple and works well.
We currently have a need to add a custom menu item to the Send To menu within our document libraries that would allow a user to create a link to the currently selected list item within another library. When the user clicks on the new "Send Link to..." menu item, they should be prompted to browse to the library in which the link should be added. Once the user chooses a destination, the link, along with the metadata from the list item, should magically appear in the selected desitnation library. Once again, we only want a link, not a copy of the file. Is this possible to do? Code examples would be much appreciated.
Does it have to be in the send to menu? Can it also be directly in the context menu (say at the bottom)? If so, you can create a feature that deploys a CustomAction to the site. If it really, REALLY needs to be under the "send to" menu, you are going to have to use javascript (since that is how the out of the box context menu is created) to "hijack" the menu and insert your own item.
IMHO this is rarely needed, a CustomAction is the preferred way of doing this. It is the easiest and most "maintainable" (all it is is a feature + customaction definition with maybe some code, all of which are deployed using a solution).
More info on CustomActions here.
P.S. if you do decide to go with javascript, don't go editing the out of the box sharepoint js files in SharePoint's 12 Hive, but add a ContentEditorWebPart to the page and insert your Javascript in there.
P.P.S. While assigning a method from an assembly as the action for a CustomAction is allowed in most cases, it is not for the ListEdit (item) context menu.
What they say is that "Sharepoint server 2010 will have it out of the box", i.e. documents may stay where they were created and links go to the Records center (named "In Place Records Management, see http://www.cmswire.com/cms/document-management/the-scoop-sharepoint-2010-records-management-005948.php).
MOSS 2007 requires the actual document to be copied to the Records repository to be registered.