Bo Wang's dashboard

Hi Stuart,

I think the regex filters must match the text exactly so things like "." will not work since it will only match 1 character (only a partial match), and "[^ ]*" would match only titles without spaces within them (the condition basically says that the text can contain anything except spaces).

I tend to use an online regex tester to aid my reports when using regex based text filtering, one that I use often is http://regexpal.com , be careful that the regex tester and the plugin sometimes have different behavior, but for normal usages it works quite well in developing useful regex expressions.

I hope this has helped.

Have a merry Christmas and I wish you the best of luck in your adventures through Reporting and Scaffolding (2 of my favourite Confluence plugins due to the high level of flexibility :))

Regards,
Bo Wang

Hi,

This should be possible, I regularly use nested macros/user macros within my reports to get the most out of the reporting plugin using injection (the body will have any '%prefix:keychain%' values injected with values from the current report item prior to being rendered), taking the original user contact card:
------------------
{report-block}

{user-reporter}
{text-sort:user:full name}
{user-reporter}

{report-body}
{float:left}
{report-image:user:picture|width=16px|height=16px} *{report-info:user:full name|link=true}*
*User ID:* {report-info:user:name}
*Email:* {report-info:user:email|link=true|default=_Unavailable_}
{float}
{report-body}

{report-block}
------------------

We can switch the recipe to use injection by setting "injected=true" in the report-body macro:
-----------------
{report-block}

{user-reporter}
{text-sort:user:full name}
{user-reporter}

{report-body:injected=true}
{float:left}
{report-image:user:picture|width=16px|height=16px} *{report-info:user:full name|link=true}*
*User ID:* {report-info:user:name}
*Email:* {report-info:user:email|link=true|default=_Unavailable_}
{float}
{report-body}

{report-block}
-----------------

Then we can add your user macro with an injected parameter:
-----------------
{report-block}

{user-reporter}
{text-sort:user:full name}
{user-reporter}

{report-body:injected=true}
{float:left}
{report-image:user:picture|width=16px|height=16px} *{report-info:user:full name|link=true}*
*User ID:* {report-info:user:name} ( {whoiswho:%user:name%} )
*Email:* {report-info:user:email|link=true|default=_Unavailable_}
{float}
{report-body}

{report-block}
-----------------

This should inject the user's username into the whoiswho macro, try it out and let us know how it goes.

We wish you a merry Christmas and a happy holiday~

Regards,
Bo Wang

Hi Laurence,

Are you by chance using the rich text editor and switching between the rich text editor and wiki markup?

This is a known side effect when switching between rich text editor and wiki markup editor, sometimes characters get inserted before macros which breaks them, so basically if you have a "\" in front of the "|" it breaks the table.

Be careful when using complex macros in rich text editor, I recommend just setting wiki markup as your default editor when setting up scaffolding pages to avoid getting this problem.

Regards,
Bo Wang

Hi Laurence,

From a brief analysis of the reporting/scaffolding macro usage you provided in your post, I noticed one thing which may be causing the problem, within the reporting table, you are reporting on "data:ValueFlows", however, in the scaffolding table, you specified the name as "cards".

If you modify the {table-data:cards} to be {table-data:ValueFlows}, it should work as expected.

Please let us know if you are coming across any further issues.

Regards,
Bo Wang

Hi,

You can do this by using the various filters to limit the list of pages in your results, here is an example of getting a list of all pages (that are descendents of the current page) that has 0 attachments.

{report-block}
{local-reporter:descendents}
{text-filter:attachments > size|include=0}
{local-reporter}
{report-body:injected=true}
%title% has %attachments > size% attachments
{report-body}
{report-block}

Regards,
Bo Wang

Hi,

I have just tested this and have had the same behavior, I think this is because of the way that scaffolding works, it deals with labels a bit differently to the default add page action (the default add page action reads the parameter in from the URL parameters, which is what the add-page-form macro relies on).

Please raise an improvement issue here: http://greenhouse.customware.net/jira... and we will look at incorporating this functionality in future releases of the plugin.

Regards,
Bo Wang

Hi Martin,

Try the homepage for Suppliers ( http://www.customware.net/repository/... ), it has a list of all of the suppliers available as part of our plugins, with a brief explanation of how supplier chaining works (towards the bottom of the page).

The concept behind suppliers is that they do not return literal values, they actually return objects, if you use the object directly, it is very similar to calling the .toString() method for that object, using supplier chaining, you can access the attributes of the object.

Hope the documentation helps, let us know if it is unclear and we will try and improve it.

If you are curious on how it works behind the scenes, feel free to check out the source code from http://svn.atlassian.com/svn/public/c... and take a look around.

Regards,
Bo Wang

Hi Martin,

I am not sure if you have tried chaining the suppliers yet.

Basically, when you see the output as "page: Integration_Platform v.2 (295131) ", it means the data you are reporting on is a page object and contains all of the data that relates to the page, to get the page title, you will need to add " > content:title" to the end of your injection value so instead of:
%data:provider%
you will need to put:
%data:provider > content:title% (ie. get the "title" attribute from the object)

This should give you what you are looking for.

Regards,
Bo Wang

Hi Carl,

I'm glad this solves your problem.

I have forwarded your comment to the tech writers in charge of the documentation on the site and will have it updated to reflect your comments, thanks for your suggestions.

Regards,
Bo Wang

Hi Carl,

When configuring your SalesForce username/password, are you using your normal password that you use to log into SalesForce?

The password actually requires your security token appended to the end of it, so assume your password is "mypass" and your security token is "XXXXXXXXX" then your configured password in the connector should be "mypassXXXXXXXXX".

Please let us know if this solves your problem.

Regards,
Bo Wang

Hi Dan,

Good to hear from you, I agree completely with that, I'll be looking into updating it with some details about using both the SDK as well as the the new AMPS maven plugin (very keen on checking out the source code for this as soon as I get back to Sydney) :)

Hi Michael,

Thanks for raising this to our attention.

This looks like it might be an URL encoding issue, please raise an issue regarding this in our JIRA and we will take a look at this.

In the meantime, can you please try using URL encoded versions of the problematic characters, the URL encoding reference table can be found at: http://www.w3schools.com/TAGS/ref_url...

Please let us know if this is a suitable workaround for this issue.

Regards,
Bo Wang

Hi Christian,

This should be possible, there is an example written for this kind of scenario in the Confluence Extensions space on the Atlassian website, please take a look here: http://confluence.atlassian.com/displ... in specific, refer to the Scaffolding + Reporting + Visibility = User Macro section of the guide.

This should create an editable link on your Confluence page.

Regards,
Bo Wang

Hi Brian,

I think this might be because comments themselves do not have titles so trying to sort by them will have no effect, you can however, sort the page titles as part of the local-reporter to achieve what you are looking for, here is the markup for the updated expanding-reporter:

-------------------------------
{expanding-reporter:content:all comments|as=comm}

{local-reporter:children} {text-sort:title} {local-reporter}

{date-sort:comm>creation date|order=descending}

{expanding-reporter}
-------------------------------

Let me know if this works for you.

Regards,
Bo Wang

Hi Joe,

We actually made a little video regarding this as it is one of the most commonly asked questions that we receive, you can view it here:
http://www.customware.net/repository/...

Basically, to view what has been changed, just click the Tools -> History link and you can view the historical versions of the scaffolding data, currently there is no display to show what has changed (showing the differences from version to version), but you should be able to see what was in the scaffolding fields at each version.

Regards,
Bo Wang

Hi Vijay,

This is actually already in the link-to macro, Iam unsure of the version that this was added but it definitely is in the 2.6.8 release.

The parameter to turn off the icon is "popupicon", just add popupicon=false to your link-to macro to see if it works for you, if not you may have to upgrade to get this feature.

Regards,
Bo Wang

Hi Kay,

Good to hear that one problem is resolved :)

In regards to updating the data, this is because the fields you are using in your template is the Confluence default template input fields which does not work in conjunction with live-template, to have updatable fields, please use the ones that come with the scaffolding plugin such as text-data (or any other xxx-data macro).

Please visit http://www.customware.net/repository/... to see a full list of possible macros you can use to generate the different xxx-data fields.

Regards,
Bo Wang

Hi,

You can achieve this by using the inject functionality as part of the report-block macro, try the following:

{report-block}
{local-reporter:creator}
{local-reporter}
{report-body:injected=true}
{show-to:%name%}
Stuff to show ONLY to the creator.
{show-to}
{report-body}
{report-block}

Regards,
Bo Wang

Hi Kay,

I agree with kykorner that this might be the cause as I am unable to replicate the problem using my local Confluence when referencing the template name exactly, however, with the excess white space, it is unable to find the template, make sure that your live template macro does not have any excess white space and also make sure that the template name itself does not have any leading or trailing white spaces, please let us know if you are still experiencing the problem after trying these things.

If possible, can you please raise an issue in http://jira.adaptavist.com/browse/SCAFF if one does not exist, trimming the template name to remove excess white space should be quite simple and avoid future confusion when using live templates.

Regards,
Bo Wang

Hi,

I think this might be because not all content are allowed to have comments and thus made more sense to be moved into the page suppler instead (where the comments exist),I do not think reply count exists within the page suppler however, you can just chain it by using something like:

page:all comments > collection:size

to get the number of comments on the page.

Hope this clears things up a bit.

Regards,
Bo Wang