Blog list not updating

05-Dec-2019 20:46

It holds maximum three fragments and keep destroying the off screen fragments.

It is suitable in the situation where the number of fragments are large.

* Currently Active Fragments means one which is currently visible one is before it and one is after it.

* * @param object Active Fragment reference * @return Returns the index of the currently active fragments.

Ali, Thanks, but this is something I already have set up.

The problem is that after the value is updated, everytime the item is changed (other columns that the one that trigger the workflow) the workflow restars, and in my case re-sends an email (it was set up to Actions: send an email). Thanks, You probably need two workflows, a hidden field and a "Start another workflow activity" (which can be found on Code Plex) Workflow 1 is a helper workflow which is set to start when an item is changed: It check if Status is equal to hidden field If it is the exit If not then start workflow 2 and set hidden field to current value of Status Workflow 2 is then the real workflow which does what you want when Status is changed @Marius: The first step in the workflow should be to compare the field value and provide a logic branch.

*/ @Override public int get Item Position(Object object) This method tells the adapter to force out of sync fragments to recreate its view hierarchy again(in case of Fragment Pager Adapter) or destroy fragments and recreate it(in case of Fragment State Pager Adapter and Pager Adapter) or tells that the position and state of the active page(s) are appropriate and it doesn’t need to be updated.

If we pass the data to the fragment using set Argument(Bundle), event if we force fragment to recreate its view hierarchy, it will show the old data which we have passed earlier using set Argument() method.

So Fragments are created, attached, destroyed and detached keeping the memory uses low. I want to trigger a workflow only when a value is updated in a list item, but not everytime the item is changed.For example I have a column for approve/not approve and I want that to be the trigger not the other values in the item.It is called for all the active pages of the adapter(three maximum).If the data in the fragment present in the collection we simply return its position and if new data not found in the collection we return POSITION_NONE which forces fragments to recreate its view hierarchy again with new data.

So Fragments are created, attached, destroyed and detached keeping the memory uses low. I want to trigger a workflow only when a value is updated in a list item, but not everytime the item is changed.For example I have a column for approve/not approve and I want that to be the trigger not the other values in the item.It is called for all the active pages of the adapter(three maximum).If the data in the fragment present in the collection we simply return its position and if new data not found in the collection we return POSITION_NONE which forces fragments to recreate its view hierarchy again with new data.To overcome this problem we will supply data to the fragments using a setter while creating the fragment first time and override instantiate Item() method to check whether the old data and new data are different or equal.