Adobe Community: Message List - BC.Next Requests

Re: BC.Next Requests

forums_noreply@adobe.com — Mon, 10 Nov 2014 02:59:13 GMT

thanks stephen,

yeah .. the json flag is an alternative option but I still have to run a secondary load to pull it in and then have to wait for the data to become available before I can run any scripts that are dependant.

Re: BC.Next Requests

forums_noreply@adobe.com — Mon, 10 Nov 2014 01:50:12 GMT

Hi Gary,

I like your ideas here, having a repository of JSON data auto created by BC sounds like a handy idea.

I’ve been using a similar concept by almost including all my Liquid code inside /_System/includes/ and inside this folder I place specific “functions” and random resources to create collections and run specific tasks. It’s not 100% ideal, it’s a manual process, but it works (at times).

What Liam was suggesting is you can get a JSON output on whatever page you’re after by simply applying &JSON=true at the end of the html page (I’m sure you were always aware of this). But this is not what you were after, I know.

Re: BC.Next Requests

forums_noreply@adobe.com — Mon, 10 Nov 2014 01:14:48 GMT

I’m not sure if you understood my question Liam.

I want to access the JSON data but NOT have it print in the HTML. Hence why I was asking if we could have some facility to push the JSON to localStorage on the server, or special a JS variable.

Pushing the {{this}} && {{globals}} to a page variable allows me to access the data from an external js file.

Re: BC.Next Requests

forums_noreply@adobe.com — Fri, 07 Nov 2014 11:21:13 GMT

You have all the page json stuff if you remember Gary. Any page can be set to show its contents as JSON.

Re: BC.Next Requests

forums_noreply@adobe.com — Fri, 07 Nov 2014 07:12:18 GMT

Is there any possible way have a flag or something to push the page's {{this|json}} && {{globals|json}} to something like localStorage from the server?

This would allow us to access the data array in external JS files without have to render the json data in html on the page.

Or is there currently another trick to achieve the same effect?

Re: BC.Next Requests

forums_noreply@adobe.com — Thu, 06 Nov 2014 06:44:22 GMT

Paramater passing:

You can pass a parameter into a module list layout, but this will not come through in the detail.

Is it possible to have passed paramaters in the list & Detail view?

Re: BC.Next Requests

forums_noreply@adobe.com — Thu, 06 Nov 2014 01:39:05 GMT

Re: BC.Next Requests

forums_noreply@adobe.com — Wed, 05 Nov 2014 22:00:57 GMT

mything="{{company.phone}}" then in the module..

Re: BC.Next Requests

forums_noreply@adobe.com — Wed, 05 Nov 2014 22:00:21 GMT

You can pass as a variable into those modules scott

Re: BC.Next Requests

forums_noreply@adobe.com — Wed, 05 Nov 2014 21:36:06 GMT

Can we get the {module_json} file to render inside content holders/modules from placing it on the template. For example we have a json file that is storing all company information like phone, adddress, etc. Would be great to be able to add {module_json json="/_System/Json/company.json" template="" collection="company"} to each template then from anywhere we can call {{company.phone}}

Right now it only works to call {{company.phone}} from on the template itself or within a page. Not from within content holders or modules.

Re: BC.Next Requests

forums_noreply@adobe.com — Wed, 05 Nov 2014 20:23:29 GMT

It is documented Scott, but like the BC module date, BC actually does not expose the server date in the system. I am not sure why, I forgot what Cristinel told me now. As you know the module just renders some javascript and string date for the users date / time.

What do you think of the type idea though Scott, that should solve a heap of issues I think.

Re: BC.Next Requests

forums_noreply@adobe.com — Wed, 05 Nov 2014 15:37:54 GMT

Awesome if this is already possible but if not I would like to request the ability to get the current date and time in globals. Something as simple as getting the current date and filtering out the year for the copyright would be great. I'm sure there are many more use cases for grabbing this kind of information but that is just a small one. I know shopify allows it buy doing something like this {{ 'now' | date: "%Y" }}

Re: BC.Next Requests

forums_noreply@adobe.com — Mon, 03 Nov 2014 05:05:56 GMT

I have emailed about this but I want to add it here.

BC with Liquid has a math issue. Yep there are some bugs with < etc that need to be fixed and product prices return as a string right now when they should be number values... BUT....

There is a further underlining issue here with data in this regard. BC basically returns a string for just about everything so doing math on values will be a bit of an issue throughout the system. Let's say you got a web app with custom fields for example. Your custom field value could be something that needs to be "2.4342" for example. You can not use the BC custom number field as that only accepts whole numbers (and probably still returns a string, lol) so you need to use text which will be a string.

But you may want to run liquid on that?

I do not expect the BC engineers to spend the time making sure any possible number field renders as a number and more, that would take forever.

BUT

If you BC guys could work on a custom filter to convert the value type then we could do a lot of the leg work ourselves.

This would have the following options..

boolean,

string

float

int

And convert one type to another. Most things would be a string to one of these other types though. This would solve a lot of this math or possible value type conflicts when people try to do if conditions etc.

Re: BC.Next Requests

forums_noreply@adobe.com — Mon, 03 Nov 2014 04:42:16 GMT

Wholesale Pricing:

This is not as straight forward as it sounds of course but...

It would be great to show the wholsale price as a separate object for a product - Just for information pruposes, along with the sale price. These can just be something like...

wholeSalePrice:

originalSalePrice:

And just the values.

Why?

- Letting people know possible savings of being a wholesaler

- Showing the original price to wholesalers

- Doing math on the prices to show the discount saved

Re: BC.Next Requests

forums_noreply@adobe.com — Mon, 03 Nov 2014 02:08:32 GMT

Some modules do not support sorting, for example: module_catalogueselect

It would be great if you pass these in a collection that your collection could handle the BC sorting, OR its own. Syntax in liquid in other systems is below

{% for aCat in catSidebar.items order:Weight -%}

{% for aCat in catSidebar.items | order:Weight -%}

Re: BC.Next Requests

forums_noreply@adobe.com — Mon, 27 Oct 2014 22:28:46 GMT

I think It was in PAB.

Re: BC.Next Requests

forums_noreply@adobe.com — Mon, 27 Oct 2014 21:56:48 GMT

@Rob Dreaming is good right?

Cannot find the trigger thread Liam but yes, this kind of functionality would give BC one more notch in it belt to making it a complete solution. Something you otherwise need other servers for and that is overkill for often one simple tasks that many BC customers and developers cannot warrant the time & investment in.

Re: BC.Next Requests

forums_noreply@adobe.com — Mon, 27 Oct 2014 21:35:55 GMT

You mean like we are now Rob?

At Pretty we have already pitched this with triggers, being able to form requests with others and have interval operational triggers. I think there is a big pitch thread on it here as well that I wrote.

Re: BC.Next Requests

forums_noreply@adobe.com — Mon, 27 Oct 2014 21:25:16 GMT

Running code server-side on BC? You must be dreaming...

Re: BC.Next Requests

forums_noreply@adobe.com — Mon, 27 Oct 2014 21:10:34 GMT

Timer

I may be dreaming but this would be handy especially in some app building having a timer that could run code one the site automatically like running email campaigns does or schedule webapp item release date.

I understand this would most likely need to be locked down to maybe run minimum daily and maybe limit how many each site can use to stop people running continuously. There are certainly many more things to consider as well.

Use: Backup BC is an example. Run automatic backups ie. run every 1 daily at 23.45pm

This could help backups be scheduled for late at night out of peak hours.

eg {% timer recur="1d" time="2345" %} ie. backup.js {% endtimer %}

If I am dreaming or this is not possible please disregard.

Re: BC.Next Requests

forums_noreply@adobe.com — Fri, 24 Oct 2014 00:21:20 GMT

Page information in globals...

page

title: text Title of the page.
name: text Name of the page.
url: url
Url of the page.

Also, It would be great if you guys could implement the Liquid URL paramater fetching, this would be really powerful. I know you can use the module_url but you would have to assign that to a value. I can see the liquid URL paramater features on shopify for example allows more direct use.

Re: BC.Next Requests

forums_noreply@adobe.com — Wed, 22 Oct 2014 02:20:29 GMT

There are some hacks right now to get a dynamic menu going in BC for a shop catalogue but it adds to many modules and not a great way. A few people have asked me about this in just the last week.

{module_cataloguelistdump} Renders a dump of the current catalogs in a catalog

{module_cataloguelistdump catalogId="-1" collection="my_custom_collection_name" template=""}

Would render all catalogs from the root and expose them to a collection.

BUT this does not contain the children of the catalogs nor their ID's

{module_catalogueselect} Renders Catalogs in an option select output but can also be formed into a collection.

In the collection the data is the name, ID and the children of the catalogs but lacks the URL.

Catalogue list Dump module therefore should contain all the child items of each cataloge so you can properly create a custom dynamic menu as you need to.

Re: BC.Next Requests

forums_noreply@adobe.com — Tue, 21 Oct 2014 03:13:25 GMT

Campaign V3 API:

IS this coming?

Things we would like is the ability to more easily turn off and on customers email campaigns based on different conditions as well as have the current API in REST.

I am sure you guys have this down, I am just puttin ti down on paper as it were. Appreciate all the work done and how much still to do!

Doing an awesome job as a note, THANK YOU!.

Re: BC.Next Requests

forums_noreply@adobe.com — Tue, 21 Oct 2014 01:09:29 GMT

I agree with Liam.

Normally I have to have inline CSS to hide/show only the table cells and rows I want shown in the email back to customers.. and even workflows.

Long story short, please make webformresults data accessible with Liquid

Re: BC.Next Requests

forums_noreply@adobe.com — Tue, 21 Oct 2014 00:52:26 GMT

{module_webformresults} - Liquify Please

Why?

Everyone has wanted to modify the formatting of this and run different things on the data. Exposing this to liquid will address all of this without having to change the module output or provide a layout by BC.

Re: BC.Next Requests

forums_noreply@adobe.com — Mon, 20 Oct 2014 19:47:02 GMT

As Liam said above Cristinel to do what you can do in admin already giving the ability to let some users edit app setting other not etc.

I have an app and I want some admin users to be able to add webapps and edit setting but other only to edit the app items created by customers all using a custom app UI.

As an added bonus getting admin user names, emails could be used to customize an individuals UI holding preference for that user then activating them on opening the app once again just like the BC admin does. Another thought this could also let you track user actions giving logs where required and many other thing too I suspect.

Thanks for looking into this.

Re: BC.Next Requests

forums_noreply@adobe.com — Mon, 20 Oct 2014 10:27:45 GMT

Just as you have things in the admin Cristinel.

For one of my apps, you may want the developers to have parts to set things up using the app for the client, but for them to be able to have option to set roles up so the client does not see those sections.

And then very similar for clients... There are lots of cases where you develop a custom solution for a bigger client who has several users but have more limited access and features (just to edit, or add content vs configuration) for some of their staff who have access.

So you can modify the menu config with your app options, but you can not detect the user type when they are viewing the app.

Re: BC.Next Requests

forums_noreply@adobe.com — Mon, 20 Oct 2014 07:17:23 GMT

Hi,

May I go one step deeper and ask why you need to customise apps based on User Roles?

Cristinel

Re: BC.Next Requests

forums_noreply@adobe.com — Fri, 17 Oct 2014 11:24:23 GMT

Get Admin User Roles inside open admin app.

Ability to get logged in admin users, User Roles from inside an open admin app using liquid. {{globals.user}}?

Why?

It would allow for customising apps based on User Roles.

Re: BC.Next Requests

forums_noreply@adobe.com — Fri, 17 Oct 2014 06:58:24 GMT

Devon, The editor will work just as it does with the current work. You can already go into your partner portal and define things.
IT is just a bit broke so will need fixing. BC already know about this.

In terms of turning things on and off - Already in the partner portal, this has not changed.

Re: BC.Next Requests

forums_noreply@adobe.com — Fri, 17 Oct 2014 01:58:51 GMT

To make the Redactor editor more relevant for our clients, I'd request two things:

1) Enable the CSS button so it works and give us a way to define what styles are included.

2) Allow us to turn certain controls on the editor on and off on a site by site basis (like the current one does).

Re: BC.Next Requests

forums_noreply@adobe.com — Tue, 14 Oct 2014 00:43:33 GMT

Markup Whitespace:

This was a thing that always annoyed me with coldfusion

Functional liquid tags - {%%} create whitespace. Liquid has the following tag format:

{%-, -%}

Which prevents the whitespace in markup rendering. BC does not support it in this way but - {% -%}

As a request could you guys look to suppress the rendered white space by default, it may be easier?

Thank You

Re: BC.Next Requests

forums_noreply@adobe.com — Fri, 10 Oct 2014 23:01:50 GMT

I don't know how difficult this is but it would be great if would could use the visual editor in pages, as well as the site walk-though. If the customer uses the page editor with all the ice tags in place they really can screw things up especially with all the section tags.

It also means that we can avoid any compatibility issues with ICE when the whole site is loaded because we can update a page without the template attached, so there's less chance a poorly prepared (or theme'd) template will make ICE unusable.

Re: BC.Next Requests

forums_noreply@adobe.com — Thu, 09 Oct 2014 23:02:02 GMT

You honestly won't believe how many times this has been requested. Not sure why BC engineers have not make classifications available in list view. Simply cannot understand why this has not been implemented yet.

Re: BC.Next Requests

forums_noreply@adobe.com — Thu, 09 Oct 2014 22:22:26 GMT

And item slug would be awesome

Re: BC.Next Requests

forums_noreply@adobe.com — Thu, 09 Oct 2014 21:58:12 GMT

This isn't a bug so didn't want to post it on the bug thread but can we PLEASE get classifications exposed in JSON on the web app item list and not just the detail?

Also, any way to separate it out by category level? right now it just renders on the detail as one long comma separated list/array..

Re: BC.Next Requests

forums_noreply@adobe.com — Thu, 11 Sep 2014 12:49:05 GMT

Thanks for the heads up Cristinel. Looking forward to it. By the way you

guys have done some great work lately!

M: 0415 193775

E: mario@twoblokeswithapostie.com

W: www.twoblokeswithapostie.com

S: mariogugi

On Thu, Sep 11, 2014 at 10:31 PM, cristinel@adobe <forums_noreply@adobe.com>

Re: BC.Next Requests

forums_noreply@adobe.com — Thu, 11 Sep 2014 12:31:27 GMT

Hi Mario,

We are looking at these. But for now we are focusing on the core work so cannot promise anything. Like you said on a separate discussion, MVP, MVP, MVP...

As for permanent tokens, we'll definitely be included at some point, but not expect them in the following 3 months.

Cristinel

Re: BC.Next Requests

forums_noreply@adobe.com — Thu, 11 Sep 2014 11:25:48 GMT

Is someone from BC looking at this or @Liam are you using it as some wishing well? Anyway, permanent API tokens would be nice. The new REST APIs are great but we need this to fully utilise them.

Re: BC.Next Requests

forums_noreply@adobe.com — Wed, 27 Aug 2014 05:09:37 GMT

Could you add the toolbox to the product editor as well please. Anywhere it does not work in at the moment would be great.

Your limited to what you can do with products so being able to access insertion of modules etc would be helpful.

Re: BC.Next Requests

forums_noreply@adobe.com — Tue, 26 Aug 2014 13:07:19 GMT

Shipping:

Shipping as a collection if possible please.

Re: BC.Next Requests

forums_noreply@adobe.com — Tue, 26 Aug 2014 06:57:55 GMT

Shopping Cart:

{{this}} exposes a fair amount of the cart information but I currently do not see a collection for the products themselves.

If you guys have not got to this and when you do, could you please try and expose the product object in full.

The hope from us all is that with liquid we tap into the data and use it as we need to, if it exposes only the same data as tags it is a bit limiting still.

Things like showing or being able to use shipping weight information is really needed with the limitations of the shipping.

We at Pretty for example have looked at some options for custom shipping solutions which we can do enough of what we want, but when you need product weight to help form that solution or calculate total weight of the cart - We hit roadblocks.

If with liquid or now we were able to add data-weight=".... to product data and have a nice product collection loop for our cart with the data we want, we can then do more then shipping allows us until you guys improve shipping.

Basically allowing us to do something more until you guys do the ultimate updates, but that weight can be long so at least allowing us to do a bit more with more data is really important.

Re: BC.Next Requests

forums_noreply@adobe.com — Thu, 14 Aug 2014 07:45:33 GMT

Site structure and what we do will (not may, or could, will) get Messy Lucian without includes.

As a developer I hope you can understand that, Already seeing things to messy and disorganised and a release of liquid that off the bat I think is a bad start in that regard. People like us at Pretty are going to try educate people in the right way of doing things, but if you can get includes in it would be good.

I went through the liquid documentation and integration in .net on the weekend in terms of the include stuff. BC is of course it's own beast but I did not think it was all that.

Do not forget you got .tpl you can run off so something like /_System/includes/myfile.tpl

And the include tag {%include"/_System/includes/myfile.tpl"%}

Would be what we are hoping for.

Re: BC.Next Requests

forums_noreply@adobe.com — Thu, 14 Aug 2014 07:41:21 GMT

Hey guys.

External JSON source for module_json is an idea we have thought of ourselves, but in the first release this will not fit.

Regarding includes, we're taking a stab at it, but they also might not make it in the next release.

We're trying to fit many things in (with backwards compatibility of the rendering being top-priority), so at least for the first release we will have to be careful with the scope.

I hope you guys understand that some things will not fit in and that we would need to wait until a subsequent release to add more things in.

-Lucian

Re: BC.Next Requests

forums_noreply@adobe.com — Wed, 13 Aug 2014 23:45:37 GMT

Content holders to this day render funny as well, so social things do not pick up right and things do not detect properly when used in the head.

Giving us includes from what I remember in the first liquid attempt by BC - The includes did not suffer those problems.

Re: BC.Next Requests

forums_noreply@adobe.com — Wed, 13 Aug 2014 23:33:20 GMT

I second Liam's comment about includes.

Re: BC.Next Requests

forums_noreply@adobe.com — Wed, 13 Aug 2014 23:28:36 GMT

It really would be great to get some BC feedback on these requests please guys.

We at Pretty for example would REALLY REALLY like to see includes.

Again, Content holders used by clients and developers - two sides of the coin using the same feature creates a variety of issues. Includes would be a great way to protect code chunks and allow developers to create them.

Re: BC.Next Requests

forums_noreply@adobe.com — Fri, 01 Aug 2014 13:28:28 GMT

Cristinel said he had mapped out what to do for those cases rather going through this method. They are looking to increase security with apps further so I suspect that the limited hacks you can do with the parent (which is limited) will be locked down further, and they will provide alternate methods.

You are right though that liquid for both sites and apps will open the door for them to give us a bit more access to things, in saying that though it also can expose them to more things like denial of service attacks which Radu mentioned to me.

In terms of liquid you have {{globals.site}}

But I have not had any issues with my implementations for host access and document.referrer, the DOM for your app even presents the url, take a gander with your app pages in a window on their own to view what you can access.

Re: BC.Next Requests

forums_noreply@adobe.com — Fri, 01 Aug 2014 09:57:28 GMT

I have ask RaduCos about this he said they would look at it. But after listening to brass tacks about Liquid I thought I would ask here too because Liquid would be a great way to add this functionality. Not sure I am asking for anything that cannot be done already as you can use referrer and then save it to cookie, session storage etc. But it can be turned of in browsers. The BC Team app created by BC uses referrer but it can be unreliable. So even if we are given a reliable way to get url without use of referrer where referrer works then we can save it in cookie etc. doing nothing you cannot accomplish already but without the problems and extra js.

This maybe a dumb question Liam but can we get url in liquid already? If so I will try.

Re: BC.Next Requests

forums_noreply@adobe.com — Fri, 01 Aug 2014 08:54:06 GMT

That would break the restrictions they have put in place for a reason wouldn't it?

And apps are BC pages, so what works in BC sites will work in apps including liquid.